Enhance MCP server with resource handling and documentation improvements

[delano]

Implement MCP-compliant prompts and refactor resource handling with improved templating and rate limiting. Expand Postman API support and enhance error handling in the MCP server. Update documentation to reflect the new systematic approach for building Postman API functionality.

[Copilot]

Copilot reviewed 7 out of 8 changed files in this pull request and generated 1 comment.

Files not reviewed (1)

• docs/api/summaries/README.md: Evaluated as low risk

Comments suppressed due to low confidence (10)

src/tools/api/base.ts:153

• [nitpick] The error message should be more specific, indicating that the resource is not supported by the tool. Consider changing it to: Resource ${resourceUri} is not supported by this tool.

throw new McpError(ErrorCode.InvalidRequest, `Resource ${resourceUri} cannot be handled by this tool`);

src/tools/api/base.ts:141

• The listToolResources method introduces new behavior that should be covered by tests. Ensure there are tests validating the functionality of this method.

public async listToolResources(): Promise<ToolResource[]> {

src/server.ts:20

• [nitpick] The class name 'McpResourceHandler' is inconsistent with the naming conventions used elsewhere. Consider renaming it to 'ResourceHandler' for consistency.

import { McpResourceHandler,

src/server.ts:90

• The error message 'Postman API error' could be more specific. Consider including more context about the error, such as the endpoint that failed.

throw new McpError(

src/types/tool.ts:40

• The method listToolResources should have error handling to throw an appropriate error if resources cannot be listed.

listToolResources(): Promise<ToolResource[]>;

src/types/tool.ts:47

• The method getToolResourceDetails should have error handling to throw an appropriate error if the resource cannot be found or accessed.

getToolResourceDetails(resourceUri: string): Promise<ToolResource>;

src/types/tool.ts:35

• [nitpick] Consider renaming ToolResourceHandler to ToolResourceManager to better reflect its purpose.

export interface ToolResourceHandler {

src/types/tool.ts:29

• [nitpick] Define a specific type for operations to avoid ambiguity and improve readability.

operations: string[];

src/handlers/tool-handler.ts:53

• The method listToolResources is called without checking if the handler implements it. Add a check to ensure the handler has this method.

const resources = await handler.listToolResources();

src/handlers/tool-handler.ts:78

• Ensure canHandleResource returns a boolean and handles any potential exceptions.

return handler.canHandleResource(resourceUri);