One call: PDF invoice to parse (hallucination-guarded OCR) + field extraction + arithmetic verification (+optional issuer enrich). Flat $0.05/document; inputs validated before payment.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | ||
| enrich | No | ||
| x_payment | No | Optional: base64 X-PAYMENT header value (x402 exact scheme, USDC on Base mainnet). Omit it to receive the payment requirements (accepts[] + docs) for this call without being charged. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description properly discloses key behaviors: hallucination-guarded OCR, arithmetic verification, flat $0.05/document fee, and input validation before payment. It omits return format, error handling, and the exact payment flow, which are important for a paid tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two tight sentences that lead with the core value proposition, enumerate features, and include pricing and validation—all without redundancy. It is concise and well-structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema exists and no annotations are provided, yet the description fails to mention return values, failure mode, or payment request/response behavior. For a complex billing pipeline, this leaves substantial gaps in what the agent needs to know.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is only 33%, and the description adds meaningful context by explaining the 'enrich' parameter as optional issuer enrichment and implying 'url' refers to the PDF invoice. It does not discuss 'x_payment' beyond the schema's own detailed description, so compensation is partial.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states a unified PDF invoice pipeline combining OCR, field extraction, arithmetic verification, and optional issuer enrichment. This distinguishes it from sibling tools like ocr_image or verify_invoice by emphasizing the all-in-one nature.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'One call' implies using this tool instead of invoking multiple sibling tools separately, but it does not explicitly name alternatives or provide when-not-to-use guidance. Usage context is implied rather than directly stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Multiple tools have unclear boundaries: document_pipeline and parse_document both parse PDFs, portrait_analysis and style_profile both perform color analysis, enrich_company and jp_company_profile both resolve company profiles, and jp_payroll_suite bundles capabilities that already exist as separate tools. Descriptions are detailed, but an agent must carefully compare several near-synonyms before selecting.
All names are snake_case, but the conventions are mixed: get_* for metadata, jp_* for Japan-specific calculations, pdf_* for PDF operations, plus standalone nouns like meal_vision and style_profile. The prefixes help readability, but there is no uniform verb_noun pattern and ordering is inconsistent (quote_parse vs parse_document).
35 tools is far above the well-scoped 3-15 range and indicates an aggregator/marketplace rather than a focused server. Even with clear individual descriptions, the sheer breadth across OCR, PDF, Japan tax, style, and marketplace functions makes the tool set feel heavy and harder to navigate.
Within its broad marketplace scope, the server is fairly complete: paid products have free samples (get_sample), quotes (quote_parse), receipt retrieval (get_receipt), and discovery via get_catalog and search_x402_services. PDF and Japan tax coverage are extensive, though the wide domain spread means no single area feels fully exhaustive.