Skip to main content
Glama

save_request

Save a reusable sample HTTP request payload (method, path, headers, body, and scenario description) to the Simceptor Playground. Returns the created saved-request object. Call this after verifying a mock scenario with test_mock so developers and future AI sessions can discover and replay the exact test payload via get_saved_requests or the Playground 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": {
      "name": "<name>",
      "method": "<method>",
      "url": "<url>"
    },
    "name": "save_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesTarget request URL or path with path variables resolved, e.g. '/api/v1/payments' or 'https://api.simceptor.com/mock/slug/api/v1/payments'.
bodyNoOptional request body payload string (JSON, XML, or form-urlencoded).
nameYesDescriptive name for this request scenario, e.g. 'Success Case', 'Validation Error', 'Unauthorized Token'.
methodYesHTTP method to send (e.g. GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS).
headersNoOptional HTTP request headers serialized as a JSON string, e.g. '{"Authorization":"Bearer xxx","Content-Type":"application/json"}'.
mockNameNoOptional name of the associated mock API endpoint.
descriptionNoOptional explanation of what this test request validates and which rule scenario it should trigger.
projectNameNoOptional name of the associated project workspace for grouping in the Playground.
collectionNameNoOptional name of the associated collection folder.
responseStatusNoOptional expected HTTP response status code for this test case (e.g. 200, 400, 422).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / method / description
      Previous value: -"HTTP method to send (e.g. GET, POST, PUT, PATCH, DELETE)."New value: +"HTTP method to send (e.g. GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS)."
  2. Changed10 schema fields changed
    • changedInput schema / properties / body / description
      Previous value: -"Request body string (JSON or raw)"New value: +"Optional request body payload string (JSON, XML, or form-urlencoded)."
    • changedInput schema / properties / collectionName / description
      Previous value: -"Associated collection folder name"New value: +"Optional name of the associated collection folder."
    • changedInput schema / properties / description / description
      Previous value: -"Detailed description of this test scenario"New value: +"Optional explanation of what this test request validates and which rule scenario it should trigger."
    • changedInput schema / properties / headers / description
      Previous value: -"Request headers as JSON string"New value: +"Optional HTTP request headers serialized as a JSON string, e.g. '{\"Authorization\":\"Bearer xxx\",\"Content-Type\":\"application/json\"}'."
    • changedInput schema / properties / method / description
      Previous value: -"HTTP Method, e.g. POST, GET"New value: +"HTTP method to send (e.g. GET, POST, PUT, PATCH, DELETE)."
    • changedInput schema / properties / mockName / description
      Previous value: -"Associated mock API name"New value: +"Optional name of the associated mock API endpoint."
    • changedInput schema / properties / name / description
      Previous value: -"Descriptive name for this request scenario, e.g. 'Success Case', 'Validation Error'"New value: +"Descriptive name for this request scenario, e.g. 'Success Case', 'Validation Error', 'Unauthorized Token'."
    • changedInput schema / properties / projectName / description
      Previous value: -"Associated project name"New value: +"Optional name of the associated project workspace for grouping in the Playground."
    • changedInput schema / properties / responseStatus / description
      Previous value: -"Optional expected response status code"New value: +"Optional expected HTTP response status code for this test case (e.g. 200, 400, 422)."
    • changedInput schema / properties / url / description
      Previous value: -"Request URL / path, e.g. /api/v1/payments"New value: +"Target request URL or path with path variables resolved, e.g. '/api/v1/payments' or 'https://api.simceptor.com/mock/slug/api/v1/payments'."
  3. First observed

TDQS

A3.9/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 discloses the side effect (a persistent reusable record) and the return value ('the created saved-request object'), which is useful context, but says nothing about permission requirements, whether the call is idempotent, what happens on duplicate names, or error behavior.

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?

Three sentences, front-loaded with the action and resource, followed by the return value and the usage trigger. Every sentence carries weight, though the field enumeration in the first sentence is slightly redundant against the schema.

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 10-parameter write tool with full schema coverage and no output schema, the description covers purpose, return value, and the workflow position (after test_mock, discoverable via get_saved_requests). The main remaining gap is mutation semantics such as duplicate-name handling and failure modes, which is a moderate rather than fatal omission.

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 the schema already documents all 10 parameters in detail, including examples for url, headers, and name. The description's parenthetical field list (method, path, headers, body, scenario description) only restates what the schema provides and adds no format or constraint details beyond it, so the baseline 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?

States a specific verb and resource: 'Save a reusable sample HTTP request payload (method, path, headers, body, and scenario description) to the Simceptor Playground.' It also names the retrieval sibling (get_saved_requests) and the upstream verification step (test_mock), so an agent can distinguish this persistence tool from create_mock or add_mock_rule without opening another 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?

Gives an explicit sequencing rule: 'Call this after verifying a mock scenario with test_mock,' and names the alternative discovery path via get_saved_requests or the Playground UI. It lacks an explicit exclusion (e.g., when not to save, such as one-off debugging), which keeps it just below a 5.

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