Skip to main content
Glama

Compare places

compare_places
Read-onlyIdempotent

Compare several ZIPs side by side on chosen columns.

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": {
      "zips": "<zips>",
      "columns": "<columns>"
    },
    "name": "compare_places"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipsYes5-digit ZIP codes
columnsYesattribute columns to compare

Output Schema

NameRequiredDescriptionDefault
noteNo
labelsYes
placesYes
omittedNo

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so safety is covered. The description adds essentially nothing beyond that: no limits on how many ZIPs, no note on what happens with invalid or missing ZIPs, and no mention of the output shape despite a comparison result being the whole point.

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

Conciseness4/5

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

A single front-loaded sentence with no filler or redundancy. It is efficient, though the brevity borders on under-specification rather than tightness.

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

Completeness3/5

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

The tool is simple (two flat required params) and an output schema exists, so return values need not be explained. However, for a comparison tool the description should at least hint at valid column values or minimum ZIP counts, which it does not.

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?

Schema description coverage is 100%, so both parameters (zips, columns) are already documented in the schema. The description only restates that ZIPs and columns are involved and adds no format, cardinality, or valid-column guidance beyond the schema.

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

Purpose4/5

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

States a specific verb and resource ("Compare several ZIPs") plus the mechanism ("side by side on chosen columns"). It is reasonably distinguishable from siblings like rate_places or search_places, though it never names them or states the contrast explicitly.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no reference to alternatives such as search_places or rate_places. The agent must infer that this is the tool for multi-ZIP column comparison rather than lookup or scoring.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources