Skip to main content
Glama

Fetch Spur record

fetch
Read-onlyIdempotent

Fetch a record returned by search, including list, workflow, table, job, letter, message_template or personalization IDs.

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": {
      "id": "<id>"
    },
    "name": "fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRecord id exactly as returned by search, e.g. property:<uuid>

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered and the description adds only the provenance constraint on the ID. It says nothing about what happens on a missing/expired ID, or whether the response shape varies by record type, which matters because there is no output schema.

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 well-formed sentence with the action and precondition front-loaded and no filler. The trailing enumeration of record types is slightly list-heavy but each item carries selection value for the caller.

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?

The tool is simple (one required string parameter) and annotations cover its behavior, but with no output schema the description never indicates what a fetched record looks like or that the shape varies across the seven listed record types. Adequate, but an agent still has to discover the return shape empirically.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already gives the 'exactly as returned by search, e.g. property:<uuid>' guidance. The description nonetheless adds genuine meaning by naming the record-type ID namespaces the tool accepts, which the schema example (property: only) does not convey.

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?

States a specific verb (fetch) and resource (a record previously returned by search), and enumerates the supported record types (list, workflow, table, job, letter, message_template, personalization). That distinguishes it well enough from the 'search' sibling, though the bare name 'fetch' alone would not.

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 phrase 'returned by search' implies a prerequisite workflow: you must run search first and pass an ID it produced. However, there is no explicit statement of when to use this versus search, nor what to do if the record type is unknown or the ID is stale.

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