Skip to main content
Glama

Zenserp MCP by usefulapi

by io.usefulapi
OverviewDiscussionsAdmin

Search Google local and maps

zenserp_maps_search
Destructive

Google local/maps results: shops, cafes and other businesses with address, rating, phone and coordinates. Set location for accurate results. SPENDS 1 request of the monthly quota per successful call (failed calls are not charged); do not repeat a call needlessly. GET /v2/search (tbm=lcl).

Input Schema

NameRequiredDescriptionDefault
qYesThe query.
glNoCountry (gl), two letters, e.g. us, de, gb. zenserp_list_countries lists the supported codes. Default: United States.
hlNoInterface language (hl), e.g. en, de, pt-BR. zenserp_list_languages lists the supported codes.
lrNoLimit results to these languages (lr), prefixed with lang_ and joined by |, e.g. lang_fr.
tbsNoGoogle 'tbs' filter string for what the query field cannot express, e.g. qdr:w (past week).
cacheNotrue = serve a stored copy when one exists (kept 24 h, NOT charged) and store the reply when not. Default false: every call is fetched live and charged.
startNoResult offset: 0 (default) first page, 10 second page, 20 third page ... Google serves about 300 results per query.
deviceNoDevice to emulate.
fieldsNoOnly return these top-level keys of the reply (for example organic, paid_results, related_searches). Saves context; the call is charged the same.
locationNoGeolocation of the search, in Google's canonical form, e.g. 'Manhattan,New York,United States' (see zenserp_search_locations). Set it when the result depends on place, especially ads.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and non-idempotent, but the description adds the crucial operational trait that each successful call burns one monthly quota unit while failures are free, and warns against redundant calls. That is real cost/behavior context not present in structured fields.

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?

Three short, front-loaded clauses: what you get, the location caveat, and the cost model. Nothing superfluous, though the endpoint notation at the end is slightly tacked on.

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 10-parameter search tool with no output schema and full schema coverage, the description supplies the domain framing and quota model an agent needs. It omits nothing critical, as return shape and pagination are handled by the schema.

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 all ten parameters, including the cache/quota interaction. The description only redundantly echoes the location hint, adding no syntax or format detail beyond what is structured.

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?

The description names the resource precisely ('Google local/maps results') and enumerates the payload (address, rating, phone, coordinates), plus the underlying endpoint. An agent can distinguish it from generic zenserp_search, 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?

'Set location for accurate results' and the quota warning imply this is for place-dependent business lookups, but there is no explicit when-to-use-this-vs-zenserp_search guidance or stated exclusions. Usage is inferable rather than directed.

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

All Zenserp MCP by usefulapi 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