Skip to main content
Glama

search_places

Read-onlyIdempotent

Search stations, addresses, and points of interest, then select explicit place IDs to resolve ambiguous matches.

Instructions

Search stations, addresses and POIs. Select explicit IDs when ambiguous.

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": "search_places"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNo
sourceNoÎle-de-France Mobilités — PRIM
statusNook
timezoneNoEurope/Paris
warningsNo
source_urlNohttps://prim.iledefrance-mobilites.fr/
retrieved_atNo
data_licence_urlNohttps://cloud.fabmob.io/s/eYWWJBdM3fQiFNm
data_licence_noteNoPRIM product terms apply. The SIRI catalogue also references ODbL; see product metadata before redistribution.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered without the text. The description usefully signals that results can be ambiguous and may need disambiguation, but says nothing about match semantics, ranking, or paging behavior.

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 with essential information front-loaded and zero filler. The second sentence is terse to the point of being slightly opaque, since it does not say where the explicit IDs come from.

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?

An output schema exists, so return values need not be described. However, for a geocoding search with 0% schema coverage, the definition leaves the caller without guidance on query form, result shape expectations, or how to use the returned IDs — enough is missing to keep this at minimum viable.

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 0%, so the schema contributes titles only. The description hints at what the query matches (stations, addresses, POIs) but never explains query syntax, matching rules, or what limit does beyond the default of 10.

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 ("Search") and enumerates the resource types ("stations, addresses and POIs"), which is enough to tell it apart from status/departure/planning siblings by intent. It does not explicitly name or contrast any sibling, so it stops short of full differentiation.

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 sentence "Select explicit IDs when ambiguous" implies a workflow (resolve names to IDs before calling other tools) but never states when to use this versus get_stop_info or plan_journey. Usage must be inferred rather than read.

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