Skip to main content
Glama

Fetch knowledge

fetch
Read-onlyIdempotent

Fetch a provider or editorial result by its search identifier.

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
idYesIdentifier from a search result, such as "provider:acme-cloud" or "article:my-slug".

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
textYes
titleYes
metadataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / id / description
      Added value: +"Identifier from a search result, such as \"provider:acme-cloud\" or \"article:my-slug\"."
  2. First observed

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile needs no restating. The description adds nothing beyond them: it says nothing about behavior for unknown or malformed identifiers, whether missing results error or return empty, or any pagination/size considerations for open-world content.

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 front-loaded sentence with no filler, which is efficient. It is arguably under-specified rather than over-long, so brevity costs it a point on structure rather than on economy.

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?

An output schema and rich annotations carry much of the burden for a one-parameter read tool, so the minimal description is tolerable. Still, with many retrieval-style siblings, the definition should clarify when to use this versus get_content/get_provider and what happens when the identifier doesn't resolve.

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 parameter's description already explains the identifier format with examples, so the baseline of 3 applies. The phrase 'search identifier' only loosely reinforces the provenance of the id, adding little meaning beyond the schema's pattern and example.

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 states a specific verb (Fetch) and resource (a provider or editorial result) plus the keying input (search identifier), so the operation is clear. It does not distinguish this from siblings like get_content or get_provider, which likely retrieve similar resources, leaving a real ambiguity about which retrieval path to take.

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?

'by its search identifier' implies the tool is a follow-up step after a search result, which is useful implied usage guidance. However, there is no explicit when-to-use/when-not-to-use statement and no mention of the alternative retrieval siblings that an agent would need to choose correctly.

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