Fetch a single invoice with line items, payment history, and customer detail.
| Name | Required | Description | Default |
|---|---|---|---|
| invoiceId | Yes | Invoice ID |
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | Tool result payload — shape varies per tool, see the tool description | |
| summary | Yes | One-line human-readable summary of the action | |
| renderType | Yes | UI rendering hint for the result |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows this is a safe, read-only operation. The description adds that the response includes line items, payment history, and customer detail, but it does not disclose other behavioral traits such as error handling or permissions. The added value is moderate given the annotation coverage.
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 a single sentence of 12 words, front-loaded with the action verb, and every word adds meaning. No wasted text or 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 low complexity (one parameter, output schema present, strong annotations), the description adequately defines the tool's scope. The included components are mentioned, and the output schema handles return value details, so the description is complete for this context.
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 input schema fully describes the single parameter invoiceId as 'Invoice ID', giving 100% schema coverage. The description does not mention the parameter, but with complete schema documentation, the baseline score of 3 is appropriate.
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 the specific verb 'Fetch' with resource 'single invoice' and explicitly lists the included components (line items, payment history, customer detail), clearly distinguishing it from sibling tools like list_invoices or get_invoice_stats.
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 clearly conveys that this tool is for retrieving one specific invoice with full details, providing clear context for when to use it. However, it does not explicitly state when not to use it or mention alternatives like list_invoices, so it stops short of a perfect score.
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.
Many tools have overlapping boundaries, such as generate_post_cover/attach_post_cover_from_job/upload_post_cover_from_url, update_deal/update_deal_stage/mark_deal_won/mark_deal_lost, and booking status transitions (confirm/cancel/complete/mark_no_show). The catch-all execute_tool adds further ambiguity.
Nearly all tools follow a consistent verb_noun snake_case convention (create_*, list_*, get_*, update_*, delete_*, restore_*). Minor exceptions like 'clone' and 'execute_tool' are still readable and do not significantly break the pattern.
With 223 tools, the server is extremely over-scoped. Even for a full CRM platform, this many tools overwhelms context windows and makes tool selection impractical. It far exceeds the reasonable range for an MCP server.
The surface is broad but has notable gaps: no update_booking/delete_booking, no delete_product, no send_message/send_campaign (referenced but absent), and no delete_staff/resource. Some workflows dead-end or require manual approval steps.