Draft UK vehicle sales invoices from supplied deal facts, with totals and a private review link.
Prepare a UK vehicle sales invoice draft from user-supplied facts and return calculated totals plus a private review link. Ask for all required fields and explicit VAT treatment; do not invent facts, payments or terms. No account access or storage. Human review and download are required before issuing. The link contains invoice data; share only with its intended recipient.
| Name | Required | Description | Default |
|---|---|---|---|
| mot | No | Full calendar date YYYY-MM-DD; blank when not supplied. | |
| ref | Yes | ||
| tax | Yes | Explicit user-selected VAT treatment. Standard prices include VAT at 20%; do not infer eligibility. | |
| vin | No | ||
| date | Yes | Full calendar date YYYY-MM-DD; blank when not supplied. | |
| make | Yes | ||
| pxOn | No | ||
| pxV5 | No | ||
| year | No | ||
| No | |||
| model | Yes | ||
| notes | No | ||
| phone | No | ||
| price | Yes | ||
| pxReg | No | ||
| pxVin | No | ||
| stock | No | ||
| terms | No | ||
| colour | No | ||
| extras | No | ||
| seller | Yes | ||
| address | Yes | ||
| finance | No | ||
| mileage | No | ||
| pxModel | No | ||
| pxStock | No | ||
| customer | Yes | ||
| payments | No | ||
| pxLender | No | ||
| pxHistory | No | ||
| pxMileage | No | ||
| collection | No | Full calendar date YYYY-MM-DD; blank when not supplied. | |
| derivative | No | ||
| pxAllowance | No | ||
| pxSettlement | No | ||
| registration | Yes | ||
| balanceMethod | No | ||
| pxDeclaration | No | ||
| financeCompany | No | ||
| firstRegistered | No | Full calendar date YYYY-MM-DD; blank when not supplied. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the annotations (readOnlyHint, idempotentHint, destructiveHint), the description adds critical behavioral context: it states that no account access or storage occurs, that the link contains invoice data and must be shared only with the intended recipient, and that human review is required. These disclosures go well beyond what annotations provide, enhancing safety and privacy awareness.
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 with the core purpose and return values, then adding constraints. Every sentence adds value: the first states what it does and returns; the second gives usage instructions, behavioral boundaries, and a privacy caution. It is concise, well-structured, and avoids redundancy.
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?
Given the tool's complexity (40 parameters, nested objects, no output schema), the description covers the essential context: it explains the tool's purpose, what it returns, how to handle missing information, and privacy/security considerations. It does not enumerate all parameters or return details, but the schema provides the structure. The description is adequate for an agent to understand when and how to use the tool, though it could be more explicit about specific field requirements.
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?
With schema description coverage at only 13%, the description should compensate by explaining the meaning of key parameters. It does mention 'explicit VAT treatment' (relating to the 'tax' param) and warns against inventing payments/terms, but it does not clarify the majority of the 40 parameters, including nested objects like seller, customer, extras, and payments. The description offers only high-level guidance without detailing parameter semantics.
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 specific action: preparing a UK vehicle sales invoice draft from user-supplied facts, and explicitly mentions the return of calculated totals and a private review link. It distinguishes the draft nature from final issuance and gives a concrete resource, making the purpose unambiguous.
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 description instructs the agent to ask for all required fields and explicit VAT treatment, and warns against inventing facts, payments, or terms. It also notes that human review and download are required before issuing, providing clear context for when this tool is appropriate. There are no sibling tools to differentiate from, but the guidance is actionable.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
create_invoiceClaiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!
Vehicle valuations & market reports for AI assistants. Pay per report, no subscription.
Send invoices from Claude and ChatGPT. One sentence becomes a PDF with a Stripe payment link.
Invoicing you drive by talking to your AI: log time, raise invoices and track what's owed via MCP.
Add one secure layer between your agents and this server.
Only one tool exists, so there is no possibility of confusion between tools. The tool's purpose is clearly stated and distinct from any hypothetical alternatives.
The single tool name follows a conventional verb_noun pattern (create_invoice). With only one name, consistency is trivially maintained.
A single tool is appropriate for a very narrow purpose, but it feels thin compared to typical MCP servers. The scope is limited to draft invoice creation, which is coherent but minimal.
For its stated purpose of preparing a draft invoice with VAT calculations and a review link, the tool covers the core workflow. It does not provide invoice management capabilities, but these are explicitly outside its stateless, no-storage design.
