Skip to main content
Glama

delete_mock

Permanently delete a single mock API endpoint from a project workspace, including all of its conditional response rules, chaos configuration, and captured request logs. WARNING: This action is irreversible. If you only want to remove a single rule scenario from the mock, use remove_mock_rule instead.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectId": "<projectId>",
      "mockId": "<mockId>"
    },
    "name": "delete_mock"
  }
}

Input Schema

NameRequiredDescriptionDefault
mockIdYesDatabase ID of the mock API endpoint to delete (obtain from list_mocks or search_mocks).
projectIdYesDatabase ID of the project workspace containing the mock (obtain from list_projects or search_mocks).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / mockId / description
      Previous value: -"Mock ID to delete"New value: +"Database ID of the mock API endpoint to delete (obtain from list_mocks or search_mocks)."
    • changedInput schema / properties / projectId / description
      Previous value: -"Project ID"New value: +"Database ID of the project workspace containing the mock (obtain from list_projects or search_mocks)."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and does most of it well: it discloses cascade destruction of child artifacts and flags irreversibility in a WARNING. It does not mention permission requirements or what happens if mockId is invalid or already deleted, which is the remaining gap for a destructive operation.

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

Conciseness5/5

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

Two sentences, front-loaded with the destructive scope, followed by the irreversibility warning and the alternative. No filler or redundant restatement of the tool name.

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

Completeness5/5

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

For a two-parameter destructive tool with no output schema, the description covers what is deleted, that it cannot be undone, and where to go instead. Nothing an agent needs in order to call it safely is missing.

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 description coverage is 100%, and both parameters document their own type and provenance (obtain from list_mocks/list_projects). The description adds no additional parameter meaning, so the baseline of 3 applies.

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?

Names a specific verb and resource ("Permanently delete a single mock API endpoint"), scopes it to a project workspace, and enumerates what the deletion takes with it (conditional response rules, chaos configuration, captured request logs). It is clearly distinguishable from update_mock and remove_mock_rule.

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

Usage Guidelines5/5

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

Explicitly routes the agent to the correct alternative: "If you only want to remove a single rule scenario from the mock, use remove_mock_rule instead." That gives a when-not-to-use condition tied to a named sibling, which is exactly what differentiates this destructive tool from the narrower rule tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources