Retrieve vehicle details by entering its VIN to identify the vehicle for work orders, customer records, or inventory management.
Look up a vehicle in Shopmonkey by its VIN (Vehicle Identification Number).
| Name | Required | Description | Default |
|---|---|---|---|
| vin | Yes | The Vehicle Identification Number to look up |
Changes observed during successful MCP inspections.
v1.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It only states the action and resource, without disclosing behavior such as read-only nature, error handling, or what happens if the VIN is not found. It does not contradict annotations (none exist).
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 filler. It efficiently communicates the tool's purpose without unnecessary detail.
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 single-parameter lookup, the description is minimally adequate but lacks return format information and any note about uniqueness or error cases. With no output schema, an agent might be uncertain about what the response contains.
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 100%, and the schema already documents the 'vin' parameter. The description merely restates 'by its VIN', adding no new semantic meaning beyond the schema. Baseline 3 is appropriate.
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 ('Look up'), a specific resource ('vehicle'), and the exact key ('VIN'), which clearly distinguishes it from sibling tools like lookup_vehicle_by_plate and get_vehicle. The scope is unambiguous.
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 such as get_vehicle (by ID) or lookup_vehicle_by_plate. The description does not mention any exclusions or selection criteria.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.