Skip to main content
Glama
Sign In
parserbee-mcp

parserbee-mcp

Official
by ParserBee
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get an extraction

get_extraction
Read-only

Retrieve one extraction request by ID, returning the parsed invoice, receipt, purchase order, or bank statement data for downstream use.

Instructions

Get one extraction request, including the extracted data.

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

Input Schema

NameRequiredDescriptionDefault
request_idYesID of the extraction request

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.2/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes this is a safe read. The description adds useful context that the response includes the extracted data, but says nothing about what happens for an unknown or expired request_id, nor about auth or rate limits.

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 short sentence with no filler, and the key differentiator ('one') is front-loaded. It is efficient, though the brevity leaves no room for routing guidance.

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?

For a one-parameter read tool with full schema coverage, the description is minimally adequate and does note the payload content. It omits error/not-found behavior and any routing against the closely related list_recent_extractions sibling.

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% for the single request_id parameter, so the schema already carries the parameter documentation. The description adds no format, sourcing, or constraint detail beyond that, so the baseline of 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 names a specific verb ('Get'), a specific resource ('one extraction request'), and clarifies the return payload ('including the extracted data'). The word 'one' implicitly distinguishes it from the sibling list_recent_extractions, though the sibling is not named.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance, no statement of prerequisites, and no reference to the alternatives such as list_recent_extractions or extract_document. The agent must infer that this tool is for fetching a single already-created request by ID.

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

Deploy Server

Other Tools