Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_docs_invoice_json_composite

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

Instructions

[Document Utilities] Convert raw invoice text into structured JSON: number, dates, currency, line items, totals and consistency checks Measured p50 10 ms, p95 14 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://docs.caelaralabs.com.

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": "caelara_docs_invoice_json_composite"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesRaw invoice text

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It does add real behavioral context — measured p50 10 ms / p95 14 ms with a dated benchmark source, and the fact that output includes consistency checks — but it says nothing about failure behavior on unparseable text, whether extraction is deterministic, or auth requirements for the referenced endpoint.

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?

Front-loaded with the action and extracted fields, and the benchmark line is compact. The two sentences run together without punctuation between 'consistency checks' and 'Measured p50', which slightly hurts readability, and the endpoint URL is low-value for tool selection.

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 tool with no output schema, the description usefully enumerates the returned fields, which is the main thing an agent needs. The remaining gap is error and edge-case behavior for malformed invoice text.

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 single parameter is fully documented in the schema ('Raw invoice text'), so the baseline applies. The description reinforces that the input must be unstructured raw text rather than a pre-parsed object and hints at what the text must contain, but adds no format, size, or language constraints beyond that.

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 gives 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). It implicitly separates itself from the format-conversion siblings (CSV, XML, HTML) by naming the input as raw invoice text, though it never explicitly routes against them.

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 should supply unstructured invoice text and expect structured fields back. There is no statement of when to prefer this over caelara_docs_csv_to_typed_json or the universal_data_bridge sibling, and no prerequisites or exclusions are given.

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