Skip to main content
Glama

find_place

Read-onlyIdempotent

Find transit stop groups and neighborhoods by name and get their lat/lon (znajdz przystanek lub osiedle po nazwie). Use the coordinates as input for the other tools.

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": {
      "query": "<query>"
    },
    "name": "find_place"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesName fragment, e.g. 'Kabaty', 'Rondo ONZ', 'Mokotow'. Diacritics optional.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, so the safety and determinism profile is covered. The description adds the pipeline hint about coordinates feeding other tools, but says nothing about result ambiguity (multiple partial matches), what happens on empty results, or how many candidates come back by default.

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?

Two short sentences, front-loaded with the action and followed by the downstream tip. The Polish parenthetical is a verbatim duplicate of the English content and adds length without new information, which keeps it from a 5.

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?

An output schema exists, so return-value documentation is not the description's job, and annotations carry the safety profile. What remains is a simple two-parameter lookup, so the definition is nearly complete; only match-ambiguity and limit behavior are left unaddressed.

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 50%: 'query' is well documented in the schema, but 'limit' (default 10, max 25) is undocumented in both schema and description. The description does add entity-type semantics — the query targets transit stop group and neighborhood names, not addresses — which is real value beyond the schema, but it leaves the result-count parameter unexplained.

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 ('Find transit stop groups and neighborhoods by name') plus the return payload (lat/lon), so the agent knows exactly what comes back. It implicitly differentiates from the analysis-oriented siblings (commute_time, rent_stats, rank_*) by being the lookup entry point, but never names them explicitly.

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

Usage Guidelines4/5

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

'Use the coordinates as input for the other tools' gives clear downstream-usage context, positioning this as the first step in a pipeline feeding the sibling tools. There is no explicit when-not or no-match guidance, but no competing geocoding alternative exists among the siblings, so the omission is minor.

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