Skip to main content
Glama

fetch

Read-only

Fetch full details for a specific item returned by search. The id encodes the item type: • 'expense:' — the durable Column-Q Receipt ID returned by search, URL-encoded, e.g. 'expense:RR-123%3A%3Adrive%2Ffile%209'. Never a sheet row number: rows move when the sheet is prepended. • 'report:' — the alphanumeric Firestore document id from search or list_reports, e.g., 'report:FQqDglExofsyyQv7aYy4' • 'kb:' — the knowledge-base entry id from search Use ids exactly as returned; never alter them. Returns full text + metadata to cite. Outside Deep Research read one expense with get_expense_by_id.

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
idYesItem ID from a previous `search` or `list_reports` call. Format: 'expense:<URL-encoded Column-Q expenseId>', 'report:<reportId>' (alphanumeric Firestore doc id, ~20 chars), or 'kb:<entryId>' (knowledge-base entry id).

Output Schema

NameRequiredDescriptionDefault
idYesEchoed back from the input
urlNo
textYesFull text content for the AI to cite
titleYes
metadataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"Item ID from a previous `search` or `list_reports` call. Format: 'expense:<row>' (integer row number) or 'report:<reportId>' (alphanumeric Firestore doc id, ~20 chars)."New value: +"Item ID from a previous `search` or `list_reports` call. Format: 'expense:<URL-encoded Column-Q expenseId>', 'report:<reportId>' (alphanumeric Firestore doc id, ~20 chars), or 'kb:<entryId>' (knowledge-base entry id)."
    • changedInput schema / properties / id / pattern
      Previous value: -"^(expense:\\d+|report:[A-Za-z0-9_-]+)$"New value: +"^(expense:.+|report:[A-Za-z0-9_-]+|kb:.+)$"
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, closed-world, so the bar is lower; the description still adds real behavioral context by explaining that ids are durable identifiers rather than volatile sheet row numbers, and that the result is 'full text + metadata to cite.' It stops short of describing error behavior for malformed or stale ids.

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?

Front-loaded with the core action, then bulleted per id type — highly scannable and free of filler. The id-format bullets partially restate the schema, but they carry the additional 'never a row number' warning, so the repetition earns its place.

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

Completeness5/5

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

For a single-parameter read tool with an output schema, the description covers everything needed to call it correctly: id provenance, exact formats, the durability caveat, and the sibling to use for the narrower single-expense case. Return values need not be explained further since an output schema exists.

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 pattern already enforces the three prefixes, so baseline would be 3. The description adds meaning beyond the schema: a concrete URL-encoded expense example ('expense:RR-123%3A%3Adrive%2Ffile%209'), the ~20-char alphanumeric nature of report ids, and the rationale that row numbers must never be substituted.

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 ('Fetch full details for a specific item returned by `search`') and immediately distinguishes the three id namespaces it covers (expense, report, kb), which is exactly what separates it from siblings like get_expense_by_id and search.

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

Usage Guidelines5/5

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

Explicitly names where ids come from (`search`, `list_reports`) and routes the agent elsewhere when appropriate: 'Outside Deep Research read one expense with get_expense_by_id.' It also gives a hard usage rule — use ids exactly as returned, never alter them — and an exclusion (never a sheet row number, because rows move).

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.