Retrieve quotes for a specific customer by providing company context and customer item ID. Enables read-only lookup of customer quotes from Big Red Cloud accounting data.
Gets quotes for a specific customer.
| Name | Required | Description | Default |
|---|---|---|---|
| itemId | Yes | Customer item id. | |
| companyName | Yes | Company context name, for example YOUR-COMPANY-NAME. |
Changes observed during successful MCP inspections.
v1.4.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description only states 'Gets quotes for a specific customer' without detailing pagination, sorting, response format, or limits. Minimal transparency.
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?
Single sentence, 6 words, no waste. Efficient but could benefit from more structure or detail without sacrificing conciseness.
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 no annotations and no output schema, the description is minimal but covers the basic purpose. However, it lacks details on return type, pagination, or any prerequisites, leaving some gaps for an agent.
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?
Schema coverage is 100% and includes descriptions for both parameters. The tool description does not add any extra meaning beyond the schema, so baseline score of 3 applies.
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?
Clear verb ('gets') and resource ('quotes for a specific customer'), but does not explicitly differentiate from sibling tools like brc_list_quotes or brc_get_quote, though the customer filter is implied.
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 on when to use this tool vs alternatives (e.g., brc_list_quotes for all quotes, brc_get_quote for single quote). The description lacks any usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.