Skip to main content
Glama

Serper

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Places

places
Read-onlyIdempotent

Google Maps local business search via Serper: returns matching places with title, address, rating, review count, category, phone number, and website. Accepts query plus optional country code (gl) and location string for geo-targeting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
glNoCountry code for geolocation, e.g. "us", "gb", "de"
queryYesSearch query, e.g. "coffee shops near union square"
_apiKeyNoOptional — your own Serper API key for higher limits; omit to use the shared Pipeworx key.
locationNoLocation string, e.g. "San Francisco, California, United States"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-serper-api-key",
+    "query": "coffee shops near union square"
+  },
+  {
+    "_apiKey": "your-serper-api-key",
+    "gl": "us",
+    "location": "New York, New York, United States",
+    "query": "michelin star restaurants"
+  }
+]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate readOnly, idempotent, and non-destructive. The description adds that the tool returns matching places with specific fields, providing useful context beyond the annotations.

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?

The description is a single sentence that efficiently communicates purpose, input, and output without waste. It is front-loaded with the key action.

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 local business search tool with no output schema, the description adequately lists return fields and parameter roles. It lacks details on pagination or error handling, but these are not critical for basic usage.

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 baseline is 3. The description mentions 'query, optional country code (gl) and location string' but adds little beyond the schema.

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?

The description clearly states the tool performs 'Google Maps local business search via Serper' and specifies the return fields (title, address, rating, etc.). It is distinct from sibling tools like 'news' or 'search'.

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?

The description explains the tool accepts a query with optional country code and location for geo-targeting, implying when to use it for local business searches. However, it does not explicitly list when not to use it or contrast with siblings.

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

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