Find purchase records by criteria using query, pagination, and limits. Retrieve filtered purchase data from BoondManager to locate specific transactions quickly.
Search purchases by criteria
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| limit | No | ||
| query | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the full burden of behavioral disclosure. It only says 'search by criteria' and does not explain pagination behavior, query semantics, whether results are returned as a list, or any other operational details.
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 front-loaded sentence with no redundant wording. It is concise, though it is too sparse to fully carry the behavioral and parameter context needed.
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 tool with no annotations and no output schema, the description is incomplete: it fails to mention what data is returned, how query matching works, or any pagination behavior. An agent can infer a basic search call from the schema, but cannot confidently predict the full behavior.
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 description coverage is 0%, and the description does not compensate by explaining what 'criteria' means. The parameter names query, page, and limit are partially self-explanatory, but the description adds no semantic detail beyond the raw schema.
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 states a specific verb and resource: 'Search purchases.' It is clear that this is a search operation for purchase records, and the resource name distinguishes it from purchases_get/create/update. However, it does not specify what criteria can be used or how it differs from sibling search tools.
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 about when to use this search tool versus boond_purchases_get or other purchase-related tools. The verb 'search' implies list/filter use, but there are no explicit conditions, exclusions, or alternatives mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.