Skip to main content
Glama

SerpKite

by io.github.SerpKite
OverviewDiscussionsAdmin

Google Maps place details

place
Read-onlyIdempotent

The full listing of one place by its place_id (or cid/fid) from a maps result, or by oid from a Yandex Maps result: address, country, coordinates, time zone, categories, opening hours per weekday, website, phone, rating, description and photos. 1 credit; free when no place matches.

Input Schema

NameRequiredDescriptionDefault
cidNoDecimal customer id from a maps result (instead of place_id)
fidNoFeature id "0x…:0x…" from a maps result (instead of place_id)
oidNoYandex Maps organisation id from an engine=yandex maps result (instead of place_id; uses Yandex Maps)
countryNoCountry code, e.g. us, gb, ru
languageNoLanguage of the address, categories and hours, e.g. en, ru
place_idNoGoogle place id ("ChIJ…") from a maps result

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / oid
      Added value: +{
+  "description": "Yandex Maps organisation id from an engine=yandex maps result (instead of place_id; uses Yandex Maps)",
+  "type": "string"
+}
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world, non-destructive behavior, and the description adds a genuinely useful cost disclosure ('1 credit; free when no place matches') plus the shape of the payload. It stops short of auth requirements or rate-limit context, but the billing rule is real added value beyond annotations.

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?

Front-loaded with the primary identifier and purpose, followed by the return fields and cost. One dense sentence with little waste, though the field enumeration is long enough to be slightly unwieldy.

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

Completeness4/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 compensates by listing the returned fields, and the credit note plus the 'free when no place matches' case hint at empty results. Nothing critical is missing for a zero-required-param read tool, aside from guidance on obtaining the identifier.

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 coverage is 100%, so each identifier and its role is already documented in the schema. The description reinforces that place_id/cid/fid/oid are alternatives and notes oid routes to Yandex Maps, but adds little syntax or constraint detail beyond the schema, matching the baseline for full coverage.

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+resource: fetching the full listing of one place by identifier (place_id/cid/fid/oid). The returned field set (address, hours, rating, photos, etc.) makes the scope concrete and distinguishes it from search-oriented siblings like maps/map, though no sibling is named explicitly.

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?

Usage is implied rather than stated: the identifiers are said to come 'from a maps result' or 'a Yandex Maps result', which sketches a workflow but never tells the agent when to pick this over maps/map or what to do when the identifier is unknown. No exclusions or alternatives are named.

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

All SerpKite toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources