camelotwebtools-mcp

camelot_purchase_order_generator

Idempotent

Create professional purchase orders with vendor details, line items, and delivery terms. Specify items, quantities, costs, and payment terms to generate a structured PO document.

Instructions

Purchase Order Generator: Create professional purchase orders with vendor details, line items, and delivery terms.. Local browser processing. Canonical URL: https://www.camelotwebtools.com/tools/purchase-order-generator

Input Schema

TableJSON Schema

Name	Required	Description	Default
`items`	No	Array of line items, products, or service entries
`poNumber`	No	Purchase order tracking number (e.g. PO-2026-089)	PO-2026-001
`vendorName`	No	Vendor company name	Global Hardware Supply
`deliveryDate`	No	Estimated or requested delivery date (YYYY-MM-DD)
`paymentTerms`	No	Agreed payment terms (e.g. Net 30, Due upon receipt)	Net 30

Output Schema

TableJSON Schema

Name	Required	Description
`status`	Yes	Execution status of the tool (success or error)
`prefillUrl`	Yes	Direct deep-link URL to view, edit, and export in Camelot Web Tools
`canonicalUrl`	Yes	Canonical web URL for this tool on camelotwebtools.com
`documentTitle`	Yes	Title of the generated document, report, or calculation output
`documentMarkdown`	Yes	Complete structured output and body formatted in clean Markdown

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 16, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already cover readOnlyHint=false, idempotentHint=true, and destructiveHint=false. The description adds one relevant behavioral detail, 'Local browser processing', but does not disclose output behavior, download format, or browser interaction specifics beyond that.

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?

The description is short and front-loads the core action in the first sentence. Minor blemishes are the redundant 'Purchase Order Generator:' prefix and the double period, but overall it is appropriately sized.

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?

Given that all parameters are optional, fully documented in the schema, and an output schema exists, the description provides enough contextual information for an agent to invoke the tool. The only notable gap is the lack of sibling differentiation, but this is not critical for invocation.

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 description coverage is 100%, so the schema fully documents all 5 parameters. The description mentions vendor details, line items, and delivery terms, which loosely map to parameters, but adds no meaning beyond what the input schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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: 'Create professional purchase orders with vendor details, line items, and delivery terms.' This clearly identifies what the tool does and distinguishes it from sibling tools like invoice_generator or statement_of_work.

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?

The intended use is strongly implied by the name and description ('Purchase Order Generator', 'Create professional purchase orders'), but there is no explicit guidance about when to use this tool versus alternatives, nor any exclusions or conditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server