Skip to main content
Glama

Caelara Labs Document Utilities

invoice_json_composite

Convert raw invoice text into structured JSON: number, dates, currency, line items, totals and consistency checks

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": {
      "text": "<text>"
    },
    "name": "invoice_json_composite"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesRaw invoice text

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully discloses the shape of the result (which fields are extracted, plus 'consistency checks'), which substitutes partially for the missing output schema, but it says nothing about failure behavior on unparseable text, partial extraction, or whether consistency failures raise errors or are returned as flags.

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?

One sentence, front-loaded with the verb and output shape, with zero redundant wording. Every listed field adds information about what the conversion yields.

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 transformation with no output schema, the field enumeration is the right kind of content, but terms like 'consistency checks' remain undefined and error behavior is unaddressed. Adequate rather than complete.

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% for the single 'text' parameter ('Raw invoice text'), so the schema already documents the input. The description restates that the input is raw invoice text but adds no constraints on length, encoding, or expected language/format, 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?

The description states a specific verb and resource ('Convert raw invoice text into structured JSON') and enumerates the extracted fields (number, dates, currency, line items, totals, consistency checks). The 'raw invoice text' input framing distinguishes it in practice from the sibling converters csv_to_typed_json and xml_to_json_clean, though it never names an alternative explicitly.

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: an agent can infer it applies when it holds unstructured invoice text. There is no statement of when to prefer it over the sibling conversion tools, no prerequisites, and no exclusion for non-invoice input.

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