Skip to main content
Glama

SpiceFactory Public Knowledge

Read an Essay or Case Study

fetch
Read-only

Call this after search to read one result in full. Takes the result's id or its URL. Returns the document as Markdown with its title, canonical URL, content type, and publish date for essays. Public, no auth.

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
idYesThe id of a search result (e.g. 'case-studies/z9-security'), or the result's URL

Output Schema

NameRequiredDescriptionDefault
idYes
urlYesCanonical URL to cite.
textYesThe document as Markdown.
titleYes
metadataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description still adds genuinely useful context beyond them: the access model ("public, no auth") and the shape of the returned document. Return-format detail is partially redundant given an output schema exists.

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 short sentences, front-loaded with the sequencing instruction before the input and output details. Little waste, though the return-format sentence overlaps with what the output schema already conveys.

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 an output schema and full annotations, the definition covers when to call it, what to pass, the auth posture, and what comes back. Only error/not-found behavior is left 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% and the single `id` property already documents that a URL is acceptable, so the description's "takes the result's id or its URL" largely restates it. No additional format, example, or fallback behavior is supplied beyond the schema.

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?

"Call this after search to read one result in full" pairs a specific verb (read) with a specific resource (one search result), and the second sentence clarifies the identifier forms. It is immediately distinguishable from the sibling `search`, which is named as the preceding step.

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?

The description gives an explicit trigger condition (after a search, to read one result in full) plus the input forms accepted (id or URL), which is enough for an agent to pick it over `search`. It stops short of stating when not to use it or what to do if the id is unknown.

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