Skip to main content
Glama
Sign In
Shopmonkey MCP Server

Shopmonkey MCP Server

by AbbottDevelopments
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

lookup_vehicle_by_plate

Retrieve vehicle information by license plate and region from Shopmonkey.

Instructions

Look up a vehicle in Shopmonkey by its license plate and region.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "region": "<region>",
      "plate": "<plate>"
    },
    "name": "lookup_vehicle_by_plate"
  }
}

Input Schema

NameRequiredDescriptionDefault
plateYesLicense plate number
regionYesRegion/state code (e.g., US-CA, US-TX)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.1

TDQS

A3.6/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, and the description does not disclose any behavioral details such as read-only nature, potential errors, or side effects. It only states the basic action without elaboration, so the description carries the full burden and falls short.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, concise sentence that immediately states the verb and resource. It is front-loaded, contains no unnecessary words, and effectively communicates the tool's core function.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple lookup operation, the description adequately conveys what the tool does and the inputs it requires. It does not mention output format, but the absence of an output schema and the straightforward nature of the lookup make this acceptable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already provides descriptions for both parameters ('License plate number' and 'Region/state code'), so the coverage is 100%. The tool description adds no extra meaning beyond repeating the purpose, so it does not enhance the parameter understanding beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function: looking up a vehicle by license plate and region. It identifies the resource (vehicle) and the specific identifiers (plate and region), and it is easily distinguishable from sibling tools like lookup_vehicle_by_vin.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains what the tool does but does not explicitly mention when to prefer it over alternatives (e.g., lookup_vehicle_by_vin). It provides no conditions or context for use, leaving the agent to infer when this lookup is appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools