Skip to main content
Glama

get_extraction

Retrieve a stored extraction result by document ID, including per-field confidence scores, to review and verify structured data pulled from insurance documents.

Instructions

Fetch a stored extraction result, including per-field confidence, by document id.

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": {
      "document_id": "<document_id>"
    },
    "name": "get_extraction"
  }
}

Input Schema

NameRequiredDescriptionDefault
document_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does disclose that the result contains per-field confidence scores, which is useful behavioral/return context. It does not state that the operation is read-only, whether it errors on a missing document, or whether the extraction must have been generated previously.

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?

A single front-loaded sentence with no filler, leading with the action and resource before the lookup key. Nothing is wasted, though it is terse enough to omit useful qualifiers.

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 an output schema (so return values need no explanation), the description covers the essential purpose and return content. Missing only minor preconditions such as the extraction needing to exist.

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 compensate for the single document_id parameter. It partially does by stating the result is fetched 'by document id', clarifying the lookup key, but gives no format, source, or validity details for that id.

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 states a specific verb ('Fetch') and resource ('stored extraction result') plus the lookup key ('by document id'), which clearly separates it from extract_document (which would run extraction) and list_low_confidence_fields. It lacks an explicit contrast to a sibling, so it sits at 4 rather than 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?

Usage is only implied: the word 'stored' signals that an extraction must already exist and that this tool retrieves rather than creates one. There is no explicit when-to-use statement, no precondition about running extract_document first, and no mention of what to do if the id is unknown.

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