Skip to main content
Glama

Resolve GERS ids in batch

resolve_place_batch
Read-onlyIdempotent

Resolve up to 25 GERS IDs in a single call to get compact place rows (ID, name, category, lat, lon). Missing IDs return a not_found error without affecting the rest of the batch.

Instructions

Resolve up to 25 GERS ids to compact place rows in one call.

Collapses N place_details(id=...) round-trips into one: for each id,
resolves it via the same lookup place_details uses and keeps only a
compact row — {"gers_id", "name", "category", "lat", "lon"} — not the
full place_details payload (addresses, websites, phones, socials,
sources, brand, confidence, ...). Use place_details for full detail on
a single id. Results are returned in input order; an id that doesn't
resolve gets the standard error envelope {"gers_id", "error":
"not_found", "detail"} instead and does not fail the rest of the
batch. gers_ids is capped at 25; a longer list
returns a structured {"error": ...} rather than truncating silently.
An empty list returns {"results": []}. Budgeted like every other tool.
Returns a structured {"error": ...} instead of raising if the remote
scan fails or the places dataset is missing columns this tool depends
on.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gers_idsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Install Server

TDQS

A5/5.0
Behavior5/5

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

Annotations already mark readOnlyHint and idempotentHint true, but the description adds substantial behavioral context: the 25-item cap, order preservation, per-id error envelopes for unresolved ids, empty-list behavior, budgeted execution, and structured errors instead of exceptions on remote scan failure or missing dataset columns. This goes well beyond the annotations and fully discloses side-effect-free but potentially failure-prone behavior.

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?

The description is front-loaded with the core purpose and then adds a dense but focused set of behavioral details. Every sentence contributes: batch collapse rationale, comparison to place_details, output shape, ordering, per-id error handling, cap behavior, empty-list behavior, budgeting, and error fallback. Nothing is redundant or 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?

Given the output schema exists and annotations cover read-only/idempotent safety, the description fills every remaining gap an agent needs: max batch size, result ordering, exact compact row fields, error shapes for not-found and batch-level failures, empty-list behavior, and budget expectations. There is no missing context that would prevent correct invocation.

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

Parameters5/5

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

The schema provides only 'gers_ids' as an array of strings with zero description, so the description must carry the semantic weight. It does: it explains what the ids are (GERS ids), the maximum count, how each is resolved, the output shape, ordering, and error behavior. This is far more than the schema alone offers.

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?

States a specific verb and resource: 'Resolve up to 25 GERS ids to compact place rows in one call.' It clearly distinguishes itself from place_details by emphasizing compact rows versus the full payload, and from the singular resolve_place by the batch dimension. The purpose is immediately clear even to an agent unfamiliar with the tool.

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

Usage Guidelines5/5

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

Explicitly explains when to use this tool: to replace N place_details round-trips, and explicitly says 'Use place_details for full detail on a single id.' This gives an agent a clear decision rule and a named alternative. The behavior for empty lists and oversized batches further clarifies expected usage context.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/chuofringer/placeroot'

If you have feedback or need assistance with the MCP directory API, please join our Discord server