Skip to main content
Glama

Find places

find_places
Read-onlyIdempotent

Finds bus stops, stations and the places around them by name, in one city or in every city. Accepts common English spellings of Pakistani place names, such as Faizabad or Faiz Abad. Returns the place_id and city each other tool needs. When nothing matches in a city, it lists the stops in that city served by the most routes.

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_places"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoSearch one city network. Leave out to search every city.
queryYesPlace name in English letters, such as Liberty Chowk or Saddar.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the description only needs to add what they can't. It does that by disclosing the spelling normalization (Faizabad / Faiz Abad) and the non-obvious fallback that lists the busiest stops when a city yields no match — behavior an agent could not predict from the 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?

Four short sentences, each carrying distinct information: what it finds, spelling tolerance, what it returns, and the fallback. The most decision-relevant facts are front-loaded with no filler.

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

Completeness5/5

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

With no output schema, the description supplies the return contract (place_id and city), and for a two-parameter read-only lookup with full schema coverage nothing an agent needs to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real semantics: query accepts variant English spellings of Pakistani names, and city scoping is what triggers the empty-match fallback. That clarifies the consequence of omitting city beyond the schema's own "leave out to search every city".

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

Purpose5/5

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

The description opens with a specific verb and resource (finds bus stops, stations and nearby places) and bounds the scope to one city or all cities. It also states the output identity (place_id and city), which makes it distinguishable from siblings like list_cities or place_departures.

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?

"Returns the place_id and city each other tool needs" tells the agent this is the entry point in a lookup chain, which is genuine usage guidance. It stops short of naming a specific alternative (e.g. list_cities for browsing a whole network) or stating when not to call it.

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.