Skip to main content
Glama

get_mock_by_slug

Retrieve the complete configuration of a single mock API endpoint directly by its unique slugId (e.g. 'MOCK-5cbb91d3') without needing projectId or mockId. Returns the full mock object including default response, headers, rules array (with each rule's id and slugId), stateful expressions, webhook config, and ready-to-use mockUrl. Use this when the user shares a MOCK-xxxxxxxx badge from the Simceptor UI.

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": {
      "slugId": "<slugId>"
    },
    "name": "get_mock_by_slug"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugIdYesThe unique mock slug ID copied from the Simceptor UI badge (e.g. 'MOCK-5cbb91d3').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / slugId / description
      Previous value: -"The mock slug ID shown in the Simceptor UI (e.g. 'MOCK-5cbb91d3')"New value: +"The unique mock slug ID copied from the Simceptor UI badge (e.g. 'MOCK-5cbb91d3')."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it does substantial work: it enumerates the returned payload (default response, headers, rules array with ids and slugIds, stateful expressions, webhook config, ready-to-use mockUrl). That tells the agent what it gets and confirms the tool is a read. It does not say what happens when the slug is unknown or invalid, which is a real gap for a lookup tool with zero annotation coverage.

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?

It is front-loaded with the core action and lookup key before the return-value detail. The enumeration of payload fields is somewhat long, but with no output schema it earns its place. Minor redundancy with the schema's slugId example keeps it from a 5.

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

Completeness4/5

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

For a one-parameter read tool with no annotations and no output schema, the description supplies both the selection trigger and an inventory of what is returned, which is exactly the missing structured information. The only omission is failure behavior for an unknown slug.

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 the single slugId parameter is already documented with the same 'MOCK-5cbb91d3' example format in the schema. The description's mention of the slugId adds the distinction that it is sufficient on its own (no projectId/mockId required), which is mild added meaning. Baseline 3 applies since the schema does the heavy lifting.

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 states a specific verb and resource ('Retrieve the complete configuration of a single mock API endpoint') and immediately scopes it by lookup key ('directly by its unique slugId... without needing projectId or mockId'), which implicitly separates it from the sibling get_mock_detail. An agent can distinguish the two without opening either schema.

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

Usage Guidelines4/5

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

It gives an explicit trigger condition: 'Use this when the user shares a MOCK-xxxxxxxx badge from the Simceptor UI.' Combined with the 'without needing projectId or mockId' clause, the agent knows which situation selects this tool. It stops short of naming get_mock_detail explicitly as the alternative for the projectId/mockId path, so it is not a full when/when-not/alternative statement.

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