Skip to main content
Glama

Places in poems

gj_places
Read-onlyIdempotent

Find geotagged places named in Persian poems, within a specific book, or by place name, returning matching locations with related couplets.

Instructions

Find geotagged places (locations with latitude and longitude) named in poems, a book, or by name.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gj_places"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoSearch the place list by name (e.g. 'شیراز').
cat_idNoPlaces named across a book/category, with a few poems each.
poem_idNoPlaces named in this poem, with the couplet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds that results are geotagged with coordinates, which is genuine context beyond the annotations, but it says nothing about behavior with no parameters supplied, result volume, or pagination.

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?

A single front-loaded sentence with no filler, and the key qualifier 'geotagged' appears first. The trailing 'or by name' is slightly redundant with the leading 'named', a minor wording inefficiency.

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?

With three optional parameters, no required inputs, and no output schema, the description should clarify what an unfiltered call returns and whether parameters combine. It covers the resource and its geotagged nature but leaves the zero-parameter behavior and result shape 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 description coverage is 100%, so all three parameters are already documented in the schema, including examples. The description's 'in poems, a book, or by name' loosely mirrors poem_id, cat_id, and query but adds no syntax, format, or combination semantics beyond what the schema states; baseline 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?

States a specific verb and resource ('Find geotagged places ... named in poems') and clarifies the resource with a parenthetical definition (latitude and longitude), which distinguishes it from text-only siblings like gj_poem or gj_search. It does not explicitly name a sibling it is not, so it stops short of a 5.

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 'named in poems, a book, or by name' implies three usage modes that map onto poem_id, cat_id, and query, giving implicit guidance on when each parameter applies. However, there is no explicit when-to-use/when-not-to-use statement and no routing to alternatives such as gj_poem or gj_book for non-place lookups.

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