Search QuickBooks payment terms by name using partial matching. Retrieve results with optional pagination to locate the exact term record.
Search Term records by Name (LIKE match).
| Name | Required | Description | Default |
|---|---|---|---|
| term | Yes | Search term matched against Name with LIKE '%term%' | |
| maxResults | No | Maximum number of results to return (default: 100, max: 1000) | |
| startPosition | No | Starting position for pagination (1-based, default: 1) |
Changes observed during successful MCP inspections.
v1.4.4Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden for behavioral disclosure but only states the search method, omitting details like case sensitivity, search scope, or result format.
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 efficient sentence with no wasted words, appropriately sized for the tool's simplicity.
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?
Without an output schema, the description should hint at return format but does not; also lacks behavioral context given absent annotations.
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% with detailed parameter descriptions; the tool description adds minimal value beyond echoing the LIKE matching.
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 the tool searches Term records by name using a LIKE match, distinguishing it from sibling tools like list and get.
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 implies usage for name-based search but does not explicitly state when to use this tool over alternatives like qbo_terms_list or qbo_terms_get.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.