Parse a quoted PDF to structured Markdown (hallucination-guarded OCR for scanned pages, Japanese-strong). Get quote_id from quote_parse first; price is fixed by the quote.
| Name | Required | Description | Default |
|---|---|---|---|
| quote_id | Yes | ||
| 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 carries the full burden. It discloses paid nature ('price is fixed by the quote'), OCR quality (hallucination-guarded), and language strength (Japanese-strong), but it does not explain the payment flow (e.g., omitting x_payment returns requirements) or error handling, leaving gaps.
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 sentences, front-loaded, and every word adds value. It efficiently covers purpose and prerequisite without fluff.
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 annotations or output schema exist, so the description should explain more about return format and behavior. It mentions 'structured Markdown' but lacks details on content or the payment flow, which is only in the schema. At a minimum, it covers the core purpose and prerequisite.
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?
The schema has 50% coverage, with quote_id lacking a description. The description adds meaning by stating the quote_id comes from quote_parse, compensating for the gap. x_payment already has a detailed schema description.
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 the tool parses a quoted PDF into structured Markdown, specifies OCR for scanned pages, and highlights Japanese-strong support. This distinguishes it from siblings like ocr_image and quote_parse.
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?
It explicitly notes the prerequisite to 'Get quote_id from quote_parse first,' giving clear context for use. However, it does not explicitly state when not to use this tool or mention alternatives, so it stops short of full exclusions.
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.