numeral_get_productGet a single product by its reference_product_id (your id). Returns the product's name, product_category, and timestamps. Numeral: GET /tax/products/{reference_product_id}.
| Name | Required | Description | Default |
|---|---|---|---|
| reference_product_id | Yes | Your product id (the reference_product_id used when the product was created). |
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 declare readOnlyHint=true, confirming no side effects. The description adds value by specifying the returned fields and the underlying API endpoint, providing transparency beyond the annotation.
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?
Two sentences: first states purpose and identifier, second lists returns and API. No wasted words; front-loaded with key 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?
For a simple read tool with one parameter, the description is sufficient. It states what is returned and how to specify the product. No missing information given the tool's complexity and lack of output schema.
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 lone parameter reference_product_id is well described in the schema and the description adds context (your id). Schema coverage is 100%, so the description enhances understanding without redundancy.
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 title and description clearly state the tool retrieves a single product by its reference_product_id. It specifies the returned fields, distinguishing it from sibling tools like numeral_list_products and numeral_create_product.
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 explicitly states when to use the tool (to get a single product by ID) and implies that for listing or creating products, other tools should be used. No explicit exclusion of alternatives, but context is clear.
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.
Each tool has a distinct purpose with no overlap. Tax calculations, product/customer management, transaction recording, refunds, and health check are clearly separated.
All tools use a consistent 'numeral_verb_noun' pattern with snake_case. Verbs are standard (calculate, create, get, list, ping) and maintain predictability.
11 tools cover the core functionalities of tax calculation, product/customer management, transaction recording, and refunds without unnecessary extras.
Core CRUD is incomplete: missing lists for customers and transactions, and no update/delete endpoints. While key workflows are covered, significant operational gaps exist.