Merge 2-10 PDFs into one, in order. Deterministic, $0.003.
| Name | Required | Description | Default |
|---|---|---|---|
| urls | 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?
There are no annotations, so the description carries the full burden. It adds valuable behavioral details (deterministic, in-order, $0.003 cost, 2-10 limit) but does not describe the output format or whether source PDFs remain unmodified, leaving some ambiguity.
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 short, front-loaded sentences with no filler. Both sentences earn their place: one communicates the operation and constraints, the other adds determinism and pricing.
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?
For a simple merge tool without an output schema, the description covers key operation details, constraints, determinism, and cost. However, it does not explicitly state the return value or payment flow beyond the schema, leaving a moderate completeness gap.
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 describes x_payment well but leaves urls without a description. The tool description compensates by explaining the input is PDFs, limiting to 2-10, and specifying order, adding meaning beyond the raw schema.
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 uses a specific verb and resource: 'Merge 2-10 PDFs into one, in order.' It clearly states the operation and scope, and is distinct from sibling PDF tools like pdf_info, pdf_pages, and ocr_image.
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 use case is implied by the action and resource: use this when you need to combine multiple PDFs. It does not explicitly state alternatives or when-not-to-use, but the 2-10 count limit provides useful contextual guidance.
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.