locationsList EDMtrain-supported metro locations (id, city, state, lat/long). Use a location id with the events tool, or filter this list by a city/state keyword. EDMtrain covers North American metros.
| Name | Required | Description | Default |
|---|---|---|---|
| query | No | Optional filter, e.g. "Los Angeles", "TX", "Brooklyn". |
Changes observed during successful MCP inspections.
Input schema / examplesAdded value: +[
+ {
+ "query": "Los Angeles"
+ },
+ {
+ "query": "TX"
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds minimal behavioral context beyond scope (North American metros) and the fact it's a list. No contradiction, but little extra value.
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?
Two sentences, front-loaded with the verb 'List', and every sentence is informative with no unnecessary words. Highly concise and well-structured.
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 the simple one-parameter tool with comprehensive annotations and no output schema, the description is complete: it lists the return fields, explains usage with events, and defines scope. No gaps identified.
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 a good parameter description. The description reinforces that the query filters by city/state keyword, adding no new details beyond what the schema provides. 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 clearly states the tool lists EDMtrain-supported metro locations with specific fields (id, city, state, lat/long). It distinguishes from the sibling 'events' tool by mentioning using location id with it.
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 provides clear usage context: use this tool to get location IDs for the events tool, and optionally filter by city/state. It also specifies geographic coverage (North American metros). It does not explicitly exclude alternatives, but the guidance is sufficient.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.