Skip to main content
Glama

Fetch one AMIRA record

fetch
Read-onlyIdempotent

Read a typed search result as a cited document. Full text/transcripts are opt-in and pageable; metadata and text respect exposure policy. Unknown ID returns an error.

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
idYesA typed record id from search (item:9902, pub:30001, video:…, podcast:…, project:…, section:…) or resolve_entity
max_charsNoCap on the whole returned text body, default/max 25000
fulltext_offsetNoStart offset into the full text (chars), with include_fulltext
include_fulltextNoDefault false — set true to append a publication's extracted full text
transcript_offsetNoStart offset into the transcript (chars), with include_transcript
fulltext_max_charsNoMax full-text characters to return (default/max 25000)
include_transcriptNoDefault false — set true to append the video/podcast transcript
transcript_max_charsNoMax transcript characters to return (default/max 25000)

Output Schema

NameRequiredDescriptionDefault
idNo
urlNo
textNo
titleNo
metadataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / max_chars / minimum
      Added value: +1
    • removedOutput schema / properties / error
      Removed value: -{
      -  "description": "Present instead of the record when the id is unknown",
      -  "properties": {
      -    "code": {
      -      "type": "string"
      -    },
      -    "message": {
      -      "type": "string"
      -    },
      -    "suggested_tool": {
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "code",
      -    "message"
      -  ],
      -  "type": "object"
      -}
  2. Changed5 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / additionalProperties
      Removed value: -false
    • removedOutput schema / properties / error / additionalProperties
      Removed value: -false
    • removedOutput schema / properties / metadata / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
  3. Changed6 schema fields changed
    • removedInput schema / properties / fulltext_max_chars / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / fulltext_offset / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / max_chars / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / max_chars / minimum
      Removed value: --9007199254740991
    • removedInput schema / properties / transcript_max_chars / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / transcript_offset / maximum
      Removed value: -9007199254740991
  4. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"A typed record id from search (item:7392, pub:30001, video:…, podcast:…, project:…, section:…) or resolve_entity"New value: +"A typed record id from search (item:9902, pub:30001, video:…, podcast:…, project:…, section:…) or resolve_entity"
  5. Changed2 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"A typed record id from search: item:7392 | pub:30001 | video:39218 | podcast:39121 | project:37700 | section:218"New value: +"A typed record id from search (item:7392, pub:30001, video:…, podcast:…, project:…, section:…) or resolve_entity"
    • addedInput schema / properties / id / maxLength
      Added value: +1000
  6. First observed

TDQS

A3.8/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 description's job is to add what annotations cannot: that full text and transcripts are opt-in and pageable, that exposure policy constrains metadata and text, and that an unknown ID errors rather than returning empty. Those are genuinely useful operational facts, though the 'exposure policy' behavior is named without explaining its observable effect.

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 with zero filler: purpose first, then the opt-in/pageable behavior and policy constraint, then the error case. Nothing is repeated from the annotations or the schema.

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?

With an output schema present, return values need not be described, and all eight parameters are fully documented in the schema; the description covers purpose, opt-in pagination, policy scoping, and the unknown-ID error. The only real gap is how the agent should choose this tool over the per-type getters in the sibling set.

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%, so every one of the eight parameters is already documented in the schema, including defaults and offsets. The description's statement that full text/transcripts are 'opt-in and pageable' corroborates rather than extends the schema, so the baseline 3 applies.

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 uses a specific verb-plus-resource ('Read a typed search result as a cited document') and makes the scope concrete by defining what is fetched (metadata, optional full text or transcript). It never differentiates itself from the typed getters in the sibling list (get_publication, get_video, get_research_item), so the boundary is only partially drawn.

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?

Usage context is implied rather than stated: the id is sourced 'from search ... or resolve_entity', which tells the agent this is the follow-up step to a search. There is no explicit when-to-use-this-over-get_publication/get_video guidance and no when-not-to-use guidance, leaving the agent to infer the 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.