Skip to main content
Glama
delano
by delano

delete_mock

Delete a mock server by providing its unique ID to remove unused test fixtures.

Instructions

Delete a mock server

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mockIdYesThe mock server ID

Implementation Reference

  • Handler function that executes the delete_mock tool logic. Makes a DELETE request to the Postman API at /mocks/{mockId} and returns the response.
    async deleteMock(mockId: string): Promise<ToolCallResponse> {
      const response = await this.client.delete(`/mocks/${mockId}`);
      return this.createResponse(response.data);
    }
  • Routes the 'delete_mock' tool call in handleToolCase to the deleteMock method, extracting mockId from args.
    case 'delete_mock':
      return await this.deleteMock(args.mockId);
  • Schema definition for delete_mock tool: requires a 'mockId' string parameter.
    {
      name: 'delete_mock',
      description: 'Delete a mock server',
      inputSchema: {
        type: 'object',
        required: ['mockId'],
        properties: {
          mockId: {
            type: 'string',
            description: 'The mock server ID'
          }
        }
      }
    },
  • The MockTools class returns the TOOL_DEFINITIONS array (which includes delete_mock) via getToolDefinitions().
    getToolDefinitions(): ToolDefinition[] {
      return TOOL_DEFINITIONS;
  • Base class getToolMappings() associates each tool name (including 'delete_mock') with the MockTools handler instance.
    public getToolMappings(): ToolMapping {
      const toolDefinitions = this.getToolDefinitions();
      const mappings: ToolMapping = {};
    
      toolDefinitions.forEach(tool => {
        mappings[tool.name] = this;
      });
    
      return mappings;
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description should disclose behavioral traits. It only states 'Delete', giving no information about reversibility, cascading effects, or required permissions. This is inadequate for a destructive action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence with no wasted words. It is front-loaded and efficient, though minimal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple delete tool with one parameter and no output schema, the description is adequate but lacks contextual details about post-deletion effects or failure modes, which would be helpful for autonomous agents.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with a well-described mockId parameter. The description adds no extra meaning, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Delete a mock server' uses a clear verb ('Delete') and specific resource ('mock server'), distinguishing it from sibling tools like create_mock, update_mock, and get_mock.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives (e.g., unpublish_mock) or any prerequisites (e.g., existing mock). Agents receive no context about appropriate use cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/delano/postman-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server