Skip to main content
Glama

fetch

Read-only

Fetch the full Outdoors record for a search result id (e.g. "trail:bear-lake-loop", "park:rocky-mountain-national-park", "journal:half-dome-yosemite"). Returns the complete text of the record plus the canonical theoutdoorsapp.com URL for citation.

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
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the annotation carries the safety profile. The description adds genuinely useful behavioral detail by disclosing what comes back: the complete record text plus a canonical URL for citation. It says nothing about invalid or unknown ids, error behavior, or size/length characteristics of the returned record.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero filler. The action and input are front-loaded, and the return contract (full text plus citable URL) follows immediately; the examples earn their space by demonstrating the id format.

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 annotations covering safety and no output schema, this covers the essentials: what it does, the shape of the required id, and what the caller receives. The only meaningful gap is error semantics for ids that do not resolve, which is minor at this complexity.

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 0%, so the description must carry the parameter on its own, and it largely does: it specifies that the single 'id' is a prefixed search-result identifier and supplies three format examples covering different namespaces. It stops short of stating that the id must be passed verbatim from search output or how to handle a malformed prefix.

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?

The description gives a specific verb and resource ('Fetch the full Outdoors record') and pins down the input as a prefixed search-result id, with three concrete examples ('trail:bear-lake-loop', 'park:...', 'journal:...'). This distinguishes it from the type-specific getters in the sibling set (trails.get, parks.get) by making clear it is id-driven and cross-type, though it never states that contrast outright.

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 phrase 'for a search result id' establishes the precondition that the id originates from a search call, and the illustrative ids show the accepted namespaces. There is no explicit when-not guidance or named alternative (e.g. when to prefer trails.get over fetch), which keeps it 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