Skip to main content
Glama

mock_endpoint

Return a fabricated HTTP response for requests matching a URL pattern in a Mac or iOS Simulator app, so you can test app behavior without reaching the real server.

Instructions

Answer requests to one endpoint in a simulator app with a made-up response, without reaching the server.

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>",
      "simulator": "<simulator>",
      "pattern": "<pattern>"
    },
    "name": "mock_endpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
appYesThe app: a bundle ID like com.me.MyApp, an app name, or * for every app in a simulator.
bodyNoThe response body, usually JSON.
delayNoSeconds to wait before answering.
statusNoHTTP status. Default 200.
patternYesRequests whose URL contains this, like api.me.com/v1/user. Use * for any text.
simulatorYesFor iOS Simulator apps: booted, any, a device name or a UDID. Leave out for a Mac app.
content_typeNoDefault application/json.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It correctly discloses the key trait that traffic is intercepted and the server is never reached, but it omits how long the mock persists, whether it overrides an existing real endpoint definition, permission requirements, and what the call returns.

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?

A single tight sentence with the core mechanism front-loaded and no filler. It could be improved slightly by adding one clause on persistence or lifecycle, but nothing present is wasted.

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?

This is a 7-parameter tool spanning both simulator and Mac targets with no annotations and no output schema, so the description must do real work. It covers the essential mechanism but leaves lifecycle, interaction with clear_endpoints, and return behavior unaddressed.

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%, with every parameter documented in-schema (app wildcards, pattern matching, status defaults, content_type default). The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

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 names a concrete action and target: intercept requests for one endpoint in a simulator app and return a fabricated response. The phrase 'without reaching the server' clarifies the mechanism, distinguishing it from a real network call, though it does not explicitly contrast with the sibling fail_endpoint or clear_endpoints.

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?

The mocking scenario is implied by 'made-up response' and 'without reaching the server', which gives an agent enough to infer when the tool applies. However, there is no explicit when-to-use/when-not guidance and no mention of the obvious alternatives, such as fail_endpoint for error simulation or clear_endpoints for removal.

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