Skip to main content
Glama

Fetch a record

fetch
Read-onlyIdempotent

Fetch the full public record for an id returned by search (for example "ngo:", "event:", "volunteer:", "fund:", "store:", "product:", "library:", "page:/about").

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, such as "ngo:<id>".

Output Schema

NameRequiredDescriptionDefault
idYes
urlYesPublic page of the record on hangel.org.
textYesFull public text of the record, in its original language unless metadata.translated is true.
titleYes
metadataYesStructured fields of the record, including recordType and contentLanguage.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "id": {
      +      "type": "string"
      +    },
      +    "metadata": {
      +      "description": "Structured fields of the record, including recordType and contentLanguage.",
      +      "type": "object"
      +    },
      +    "text": {
      +      "description": "Full public text of the record, in its original language unless metadata.translated is true.",
      +      "type": "string"
      +    },
      +    "title": {
      +      "type": "string"
      +    },
      +    "url": {
      +      "description": "Public page of the record on hangel.org.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "id",
      +    "title",
      +    "text",
      +    "url",
      +    "metadata"
      +  ],
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"search sonucundaki id."New value: +"The id of a search result, such as \"ngo:<id>\"."
  3. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds only that the record is 'public' and what id shapes are valid; it says nothing about behavior on invalid or missing ids.

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?

One sentence with the action and scope front-loaded, followed by an illustrative prefix list that earns its length by telling the agent which id forms are accepted. No redundant restatement of the title.

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 with an output schema, the description covers what it needs to: where the id comes from and what the call returns at a high level. Only failure behavior for malformed or stale ids is left unaddressed.

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 already 100%, so the baseline would be 3, but the description goes further by enumerating concrete id prefixes ('ngo:<id>', 'event:<slug>', 'page:/about', etc.), which is meaning the schema's single example does not convey.

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?

The definition states a specific verb and resource ('fetch the full public record') and anchors scope by tying the input to 'an id returned by search', which cleanly separates it from the search/list_* siblings that return ids rather than full records.

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?

It gives an explicit precondition — the id must come from a search result — which tells the agent this is a second-step call, not an entry point. It stops short of naming when not to use it or what to do if the id is unknown, so it is clear context without full routing.

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