Skip to main content
Glama
Sign In

Tulina

by ai.tulina.mcp
OverviewDiscussionsAdmin

serper_maps_sample

Read-only

Google Maps — a SAMPLE of places, geographically anchored.

⚠️ The name says what this tool does: a sample, not an inventory. It caps at ~20 results per call and biases toward ll → it silently undercounts (20 found where 60 exist, without raising an error or announcing a total). For a count or an EXHAUSTIVE list of a type of business over an area ("how many X in Y"), use serper_maps_census, which tiles the area, paginates each anchor and deduplicates server-side. Rule: exact total → census; a few top hits → this tool.

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": "serper_maps_sample"
  }
}

Input Schema

NameRequiredDescriptionDefault
llNolat/long anchor + zoom "@lat,lng,zoom" (e.g. "@45.76,4.83,12z").
cidNoGoogle customer id of a place.
numNonumber of results (max 100).
_orgNoOrg (id) de CET APPEL. `oto_list_orgs()`.
pageNoresults page (1-based).
queryNothe query (e.g. "coffee shops").
_groupNoÉquipe (id) de CET APPEL, sous son org parente.
_run_idNoOBLIGATOIRE à chaque appel dès `run_start` ou `data_claim_next` : sans lui, l'écriture sur une ligne réservée est refusée. Hérité seulement si le serveur tient un run actif — n'y compte pas.
countryNocountry code (default "fr").fr
_projectNoProjet (id) de CET APPEL — jeton PRIMAIRE. `oto_project(op='list')`.
languageNolanguage code (default "fr").fr
place_idNoGoogle id of a place, to look up directly.
_instanceNoInstance de connecteur PRÉCISE (un credential exact). `oto_instance(op='list')`.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior4/5

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

With readOnlyHint=true already covering the safety profile, the description adds genuinely non-obvious behavior: a ~20-result cap, silent undercounting with no error or total announced, and a bias toward the `ll` anchor. It falls just short of 5 because the schema advertises num up to 100 while the prose says ~20 — the agent must resolve that tension itself, and no pagination semantics for `page` are clarified beyond the schema.

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?

Front-loaded with the warning before the alternative, then closed with a one-line routing rule. Every sentence carries distinct information — the cap, the silent failure mode, the anchor bias, the alternative, and the decision rule — with no repetition of schema fields.

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?

For a 13-parameter, zero-required, no-output-schema read tool, the description covers the main risk an agent faces: mistaking a sample for a complete inventory. It does not explain the org/project/run_id scoping parameters or the default country/language behavior, but those are fully documented in the schema, so the gap is minor.

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 the schema already documents ll, cid, num, page, query, country, language, place_id and the _org/_project/_run_id plumbing. The description adds meaning only for `ll` (that results are biased toward it), which is useful but narrow; baseline 3 applies when the schema carries the parameter burden.

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+resource ('Google Maps — a SAMPLE of places, geographically anchored') and immediately names the sibling it is not (serper_maps_census). An agent can distinguish this tool from the census variant without opening either schema.

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?

Gives an explicit decision rule: 'exact total → census; a few top hits → this tool', plus the triggering question pattern ('how many X in Y'). It states both when to use this tool and when to use the alternative, leaving nothing to inference.

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

All Tulina 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