Skip to main content
Glama

Get a source document

get_document
Read-onlyIdempotent

The source meeting document for a document id from get_project with representation="full". Long filings consume model context and may be truncated; the response says when that happened. Each new or changed record counts toward 100,000 export records a month on County, State, and National plans. An unchanged record already delivered does not. Find Contact Info does not use credits on this call. On API Only and the trial, costs 1 credit per document. get_credit_balance returns the remaining balance.

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": {
      "documentId": "<documentId>"
    },
    "name": "get_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
documentIdYesFrom get_project with representation="full". Large; one id at a time.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), and the description adds substantive behavior the agent could not otherwise know: large documents consume context and may be truncated with the response signaling it, plus detailed quota/credit rules (100,000 export records/month, unchanged records free, Contact Info free, 1 credit on API Only and trial). That is exactly the kind of cost and truncation disclosure an agent needs before calling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is correctly front-loaded, followed by the truncation caveat. However, four sentences of billing and quota detail dominate the definition, and the "export records a month" phrasing reads as borrowed from an export tool and muddies which counter actually applies.

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 tool with full annotations and no output schema, the definition covers provenance, truncation risk, and cost — the decisions an agent must make. It still does not describe the returned document's shape or note the terminology mismatch between "meeting document" and "long filings," but nothing essential is missing 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 coverage is 100% and there is only one parameter, so the schema already documents documentId fully — including the same "From get_project with representation=\"full\"" wording the description repeats. The only marginal addition is "one id at a time," so 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?

Identifies the resource precisely — the source meeting document — and ties it to an id obtained from get_project with representation="full", which separates it from the sibling that returns project metadata. It is a noun phrase rather than a verb+resource statement (no explicit "retrieve/return"), so it stops short of a 5.

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?

Gives a real prerequisite: the documentId must come from get_project with representation="full", and that only one id should be requested at a time. It does not say when to prefer this over other content-retrieval siblings (e.g. get_ai_search_result) or when to skip it, so guidance is implied rather than explicit.

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