Public no-charge UK tool for gb.invoice.authenticity_duplication.assess.v1 (LIMITED). Claims are limited to the named official sources.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds 'Claims are limited to the named official sources', which gives some behavioral context about output restrictions. However, it does not elaborate on what 'named official sources' means or describe other behaviors. No contradiction with annotations.
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 concise at two sentences, but it is not well front-loaded. The first sentence leads with 'Public no-charge' and a technical identifier instead of stating the tool's purpose. While there is no wasted wording, the structure does not prioritize the most important information.
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?
Despite having an output schema and strong annotations, the description fails to explicitly state what the tool does. It leaves the core purpose ambiguous and does not explain how the tool is invoked or what context it uses (since there are no parameters). The vague 'LIMITED' and 'named official sources' add little clarity. Overall, the description is insufficient for confidently selecting the tool.
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 tool has 0 parameters, so the baseline is 4. The description does not need to add parameter semantics because there are no parameters. The empty input schema with additionalProperties is not explained, but since parameter count is zero, this is not a significant gap.
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 says 'tool for gb.invoice.authenticity_duplication.assess.v1', which essentially restates the tool name 'assess_uk_invoice_authenticity_duplication' in a technical form. It does not explicitly state that the tool assesses invoice authenticity and duplication. 'Claims are limited to the named official sources' provides some scope but does not clarify the core action.
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?
No guidance is provided on when to use this tool versus alternatives. The description only mentions 'Public no-charge' and 'LIMITED', which hint at conditions but do not explain appropriate usage or when not to use the tool. No sibling tools are referenced.
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 appear to address the same action with only country or payment-model differences, such as company_check/run_uk_company_check, approve_supplier/approve_uk_supplier, authorize_payment/run_uk_payment_authorization, and screen_restricted_party/screen_restricted_business_party. Even with descriptions, an agent will struggle to pick the intended tool reliably.
Naming mixes bare global verbs (company_check, approve_supplier, authorize_payment) with UK-prefixed variants (run_uk_company_check, approve_uk_supplier, authorize_uk_business_payment), plus free-form names like counterfactual, preflight, quote, and capabilities. There is no single consistent verb_noun or country-modifier convention across the set.
46 tools is far beyond the typical well-scoped MCP surface, and the set carries heavy duplication through global/UK/free/paid variants. While the domain may justify multiple country-specific operations, the tool count itself will overwhelm agents and make selection harder.
The server covers the main compliance lifecycle well: discovery (capabilities, preflight, quote, resolve_agent_intent), verification, supplier approval, payment authorization, invoice matching, passport issuance/refresh, and verification receipts. Minor gaps exist around explicit cancellation/revocation or list/search operations, but core workflows have no major dead ends.