Skip to main content
Glama

Get one location by id

get_location
Read-onlyIdempotent

One state, county, or city by numeric id from list_locations. Does not use credits.

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": {
      "kind": "<kind>",
      "id": "<id>"
    },
    "name": "get_location"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesNumeric id from list_locations.
kindYesWhich place type to load.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds a genuinely non-obvious behavioral fact not present in any structured field: "Does not use credits," which matters for cost-sensitive agents choosing among tools. It does not describe the returned record's shape, which is a residual gap given there is no output schema.

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 short sentences with no filler; the resource identification is front-loaded and the credit-cost note follows as a secondary qualifier. Every clause carries information an agent would otherwise have to guess.

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 two-parameter, fully-documented lookup with rich annotations, the description covers what it returns (a single place of the requested kind), where the id comes from, and its cost profile. The only shortfall is that no output schema exists and the description does not say what fields the returned location contains.

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 coverage is 100% and the schema already explains both parameters, including that id comes from list_locations and that kind is an enum of state/county/city. The description restates the id provenance but adds no syntax, format, or range meaning beyond the schema, so the baseline of 3 applies.

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?

Names the resource precisely ("One state, county, or city by numeric id") and ties it to the sibling that produces the ids, list_locations, so it is distinguishable from the listing tool. It stops short of an explicit verb like "retrieve"/"fetch", but the title and phrasing make the operation unambiguous.

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 phrase "from list_locations" implies the prerequisite workflow: ids must be obtained from that tool first, which is useful routing guidance. However, there is no explicit statement of when to prefer this over alternatives, nor any exclusions or error conditions (e.g., what happens with an unknown id).

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