Skip to main content
Glama

Fetch (connector form)

fetch
Read-onlyIdempotent

Fetch one entry by identifier as text with its url and metadata. A thin wrapper over get_mechanism for connectors that expect a search and a fetch tool. Entries describe processes in general, not the present state of any country, market or asset.

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
idYesEntry identifier returned by search.

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
textYes
scopeNoScope of the registry: what the entries are and are not.
titleYes
metadataNo
attributionNoCC BY 4.0 attribution: how an answer that uses the entries names the source.
review_noteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds genuinely new behavioral context: it is functionally equivalent to get_mechanism, it returns text with url and metadata, and its entries are process descriptions rather than current-state facts. That equivalence claim and scope caveat are the kind of information annotations cannot convey.

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?

Three short sentences: what it does, how it relates to its sibling, and what its data means. Each sentence carries distinct information and the core action leads. Nothing is padded or repeated from the schema.

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?

A single-parameter read tool with an output schema and full annotation coverage needs little more. The description nonetheless supplies the one thing structured fields cannot: that entries are general process descriptions, not live state, which prevents a whole class of misreading of the results.

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?

There is a single parameter with 100% schema description coverage, and the schema already says the id is the identifier returned by search. The description's "by identifier" restates the same meaning without adding format or provenance detail, so this hits the baseline rather than exceeding it.

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 one entry by identifier") plus the return shape ("as text with its url and metadata"), and explicitly positions itself relative to get_mechanism as a thin wrapper. An agent can distinguish it from get_mechanism and search without opening either schema.

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?

Explains the usage context clearly: this is the fetch half of a search+fetch pair for connectors that expect that shape, implying get_mechanism is the direct alternative. The final sentence also rules out a use case (present state of a country, market or asset), which is effectively a when-not-to-use constraint. It stops short of an explicit 'prefer get_mechanism if you can call it directly' instruction.

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.