Skip to main content
Glama

Get place

get_place
Read-onlyIdempotent

Values and national/state percentiles for one ZIP. Answers questions like 'is 98052 high in median income?'.

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": {
      "zip": "<zip>"
    },
    "name": "get_place"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipYes5-digit ZIP code
columnsNoattribute columns; omitted gives a short summary of setting, income, housing costs and commute

Output Schema

NameRequiredDescriptionDefault
zipYes
nameNo
stateYes
valuesYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior3/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 needs no restating. The description adds that results are framed against national and state percentiles, which is meaningful interpretive context. It says nothing about peer-group construction, caching, or rate limits, and the output schema removes the need to explain return shape.

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?

Two sentences, front-loaded with what is returned before the illustrative question. No filler, no restatement of the title, and the example does real work by anchoring an ambiguous percentile concept to a concrete query.

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?

With an output schema, full parameter documentation, and explicit safety annotations, the description only needs to establish scope and intent, which it does. The remaining gap is minor: it does not state what population the percentiles are drawn from or whether the ZIP must be US-only, which could matter for a geo tool.

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%, including the ZIP format and the columns default behavior, so the schema carries parameter meaning. The description reinforces the single-ZIP constraint ('one ZIP') but adds no syntax, format, or selection detail 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 resource (one ZIP) and a specific output (values plus national/state percentiles), which distinguishes it from comparison and search siblings by scope. It does not explicitly name compare_places as the multi-ZIP alternative, so sibling differentiation is implied rather than stated.

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 example question ('is 98052 high in median income?') conveys the intended use case well, giving an agent a concrete trigger. However, there is no explicit when-not guidance and no named alternative for comparing multiple places or for rating/scoring operations.

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