Skip to main content
Glama
Sign In

SerpKite

by io.github.SerpKite
OverviewDiscussionsAdmin

Google Maps

maps
Read-onlyIdempotent

Find places (name, rating, category, address, phone, website, place_id and cid, or oid with engine=yandex, and coordinates); the place tool returns one place's hours and full listing. Put the area in location (e.g. "Berlin, Germany" or "Kreuzberg, Berlin") or in q; ll searches around an exact point. 1 credit.

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": {
      "q": "<q>"
    },
    "name": "maps"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesSearch query
llNoMap viewport "@lat,lng,14z": search around that point
pageNo
engineNogoogle (default) or yandex (Yandex Maps, for Russia and the CIS where enabled; its places carry an oid for the place tool)
countryNoCountry code, e.g. us, de, ru
languageNoLanguage code, e.g. en, ru (Russian). Does not change country
locationNoCity-level location, e.g. "Austin, Texas, United States"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / country / description
      Previous value: -"Country code, e.g. us, de, ru. Uses shared proxy routes"New value: +"Country code, e.g. us, de, ru"
  2. Changed1 schema field changed
    • addedInput schema / properties / engine
      Added value: +{
+  "description": "google (default) or yandex (Yandex Maps, for Russia and the CIS where enabled; its places carry an oid for the place tool)",
+  "enum": [
+    "google",
+    "yandex"
+  ],
+  "type": "string"
+}
  3. First observed

TDQS

A4.1/5.0
Behavior4/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 needs no restating. The description adds real value beyond that by disclosing the cost ('1 credit') and the shape of the result set. It does not mention result count per page or what happens when `page` exceeds available results.

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?

The key scope statement is front-loaded and the sentence count is low. The middle sentence is a dense run-on of semicolon-separated clauses that takes a second read, costing it the top mark.

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 correctly compensates by enumerating returned fields (rating, category, address, phone, website, place_id/cid/oid, coordinates). For a 7-parameter search tool it is nearly complete; only pagination behavior and result volume are left unstated.

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 86%, so the baseline is 3 and the schema already documents most parameters. The description does add genuine semantics on top — the `location` vs `q` split for area specification and `ll` as a viewport-centered search — plus the yandex/oid linkage, which is why it sits at the top of the baseline rather than below it.

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?

Opens with a specific verb and resource ('Find places') and enumerates the returned fields, so the agent knows exactly what this tool yields. It also names the sibling it is not — 'the place tool returns one place's hours and full listing' — which disambiguates it from `place` and `map` without opening a schema.

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

Usage Guidelines4/5

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

Gives concrete routing rules: put the area in `location` (with example values) or in `q`, and use `ll` to search around an exact point. It also redirects to `place` for full single-place detail. It stops short of stating when to prefer `search` or `ai_mode` over this tool, so the exclusion set is incomplete.

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