Skip to main content
Glama
Sign In

Kamy

by dev.kamy
OverviewDiscussionsAdmin

Extract document (Kamy Ingest)

extract_document

Extract structured data from a PDF (invoice, receipt, contract, ID document, or any form). Returns the parsed JSON plus a public verify URL that proves the extraction matches the source. Use this when an agent needs to read an inbound document and act on it.

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": {
      "template": "<template>"
    },
    "name": "extract_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
templateYesPredefined template id. invoice/receipt for AP and POS docs, contract for legal agreements, id_document for passports/IDs, generic_form for anything else.
source_urlNoPublic URL to a PDF (preferred). One of source_url or source_base64 is required.
source_base64NoBase64-encoded PDF bytes. Use when the source isn't publicly fetchable.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior1/5

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

The description directly contradicts the annotations. readOnlyHint is false, yet the description frames the tool as a read-only operation ('read an inbound document', 'Extract'), implying no side effects. This is a serious inconsistency that could mislead an agent about the tool's side effects.

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?

The description is two sentences long, front-loaded with the action and object, and every sentence serves a purpose: stating the function and providing usage guidance plus return value details. There is no wasted text.

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?

The description explains return values (parsed JSON and verify URL) which is necessary since there is no output schema. It also covers typical input types. However, it omits any mention of side effects or persistence that the 'Ingest' title implies, and the read-only framing contradicts annotations, leaving key context incomplete.

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?

The input schema already provides 100% parameter coverage with descriptions for all three parameters. The description adds no extra parameter-level semantics beyond what the schema offers, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource: 'Extract structured data from a PDF' and enumerates common document types (invoice, receipt, contract, ID document, any form). This clearly distinguishes it from sibling tools like render_pdf or verify_pdf_signature, which serve different purposes.

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

Usage Guidelines4/5

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

The description provides explicit usage context: 'Use this when an agent needs to read an inbound document and act on it.' This tells the agent when to choose this tool, though it doesn't explicitly mention when not to use it or name alternatives. The guidance is clear but lacks exclusions.

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

All Kamy toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources