Skip to main content
Glama

clear_endpoints

Remove all endpoint failures and mocks for an app, or only those matching one pattern, to reset network simulation rules before testing.

Instructions

Remove an app's endpoint failures and mocks: all of them, or those for one pattern.

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": {
      "app": "<app>"
    },
    "name": "clear_endpoints"
  }
}

Input Schema

NameRequiredDescriptionDefault
appYesThe app: a bundle ID like com.me.MyApp, an app name, or * for every app in a simulator.
patternNoOnly remove rules for this pattern.
simulatorNoFor iOS Simulator apps: booted, any, a device name or a UDID. Leave out for a Mac app.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

There are no annotations, so the description carries the full behavioral burden. "Remove" signals mutation, but the description does not disclose irreversibility, permissions, error behavior, or effects on currently active requests.

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?

The description is a single compact sentence with the action and scope front-loaded. It contains no redundant wording.

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 three-parameter tool with fully described parameters and no output schema, the description covers the core operation. It still omits behavioral details important for a destructive clear operation, such as whether removed mocks or failures can be restored and what result is reported.

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%, so parameter meaning is already well documented. The description adds only a high-level reminder that the pattern limits removal to one pattern and that the default is all of them.

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

Purpose4/5

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

The description gives a specific verb and resource: removing an app's endpoint failures and mocks. It also states scope (all or one pattern), making the operation clear, though it does not explicitly distinguish itself from siblings such as fail_endpoint and mock_endpoint.

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

Usage Guidelines3/5

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

Usage is implied as cleanup of endpoint failures and mocks, and the all-vs-pattern choice is stated. However, it does not say when to prefer this over other endpoint tools, nor does it state prerequisites or exclusions.

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