Skip to main content
Glama

Read a stored source version

get_source
Read-only

Read saved text blocks and select the cited version; use block_start and block_limit to continue long documents in manageable sections.

Instructions

Read saved text blocks; version_id selects the version used by a citation.

    Continue long documents with block_start and block_limit.
    

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": {
      "source_id": "<source_id>"
    },
    "name": "get_source"
  }
}

Input Schema

NameRequiredDescriptionDefault
source_idYes
version_idNo
block_limitNo
block_startNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful context about paging through long documents and about version selection for citations, but it does not say what happens when version_id is omitted or how block_limit is interpreted (blocks vs. characters). No contradiction with annotations.

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?

Two short sentences with the core action front-loaded and paging guidance second. The semicolon-joined clause is slightly compressed, but no sentence is wasted.

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 exists, so return values need no explanation, and the read-only annotations cover safety. Still, for a 4-parameter tool with 0% schema coverage, the definition leaves source_id and block_limit semantics implicit, which is a real gap for correct invocation.

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 0%, so the description must carry the parameter burden. It explains version_id's role and the block_start/block_limit paging pair, but leaves source_id entirely undefined and does not clarify the unit or default behavior of block_limit beyond implying it bounds a page.

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 and resource: 'Read saved text blocks,' which distinguishes this text-reading tool from the sibling get_source_page_image. It does not explicitly name an alternative, but the resource scope (text blocks of a source) is clear enough for an agent to choose correctly.

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?

It gives concrete continuation guidance ('Continue long documents with block_start and block_limit') and explains the purpose of version_id in relation to citations. However, there is no explicit when-not guidance, no mention of prerequisites, and no reference to alternatives such as search_sources or get_source_page_image.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.