Skip to main content
Glama

Leggi un luogo

get_place
Read-onlyIdempotent

Get a place by its id from search_places, including OpenStreetMap and description attribution. Results include source attribution and public DalVivo URLs.

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": {
      "id": "<id>"
    },
    "name": "get_place"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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=false, so the safety profile is fully covered. The description adds genuinely new context about attribution obligations (OpenStreetMap, description attribution) and public DalVivo URLs, which matters for how results must be displayed. It does not say what happens when the id is unknown or malformed, leaving the error path undocumented.

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 core action and the id provenance. The second sentence partly restates the attribution idea already introduced in the first ('including OpenStreetMap and description attribution' vs 'source attribution'), which is minor redundancy.

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?

For a single-parameter read tool with rich annotations and no output schema, the description gives enough to call it and to know results carry attribution and public URLs. Missing are the id prefix format and the not-found behavior, which an agent would need for correct invocation and error handling.

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 description must carry the param burden. It does explain that the id originates from search_places, which is real added meaning, but it never mentions the required 'poi:' prefix that the schema pattern enforces, so an agent could pass a bare identifier.

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 ('Get a place by its id') and ties the id back to search_places, which tells an agent which sibling produces valid ids. It stops short of distinguishing itself from get_event or resolve_location, so it is clear but not fully disambiguated from all siblings.

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 'by its id from search_places' implies the correct workflow (search first, then fetch by id), which is useful routing guidance. There is no explicit statement of when not to use it, nor a named alternative for looking up a location that has no id yet.

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