Vera

Google Local Places

extract_local_places

Read-only

Extract Google Local Pack (3-pack) and Google Places listings for local queries. Returns place_id/cid, title, rating, review count, address, latitude/longitude, category, phone, and website. The most the call can cost is held first and you are charged for what it returns; a call that fails costs nothing.

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": {
      "query": "<query>"
    },
    "name": "extract_local_places"
  }
}

Input Schema

Name	Required	Description	Default
`gl`	No		us
`hl`	No		en
`fresh`	No
`query`	Yes
`location`	No
`idempotency_key`	No	Optional. Send the same key (16 to 128 letters, digits, _ . : -) to retry this exact call safely: a retry within 24 hours returns the first result and is not charged again.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 21, 2026

TDQS

A3.5/5.0

Behavior4/5

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

The description goes beyond the readOnlyHint/openWorldHint annotations by disclosing the billing model: the max cost is held first, you are charged for returned results, and a failed call is free. That is genuinely useful behavioral context for a paid, open-world scrape. It stops short of covering rate limits or latency, but it carries meaningful weight on its own.

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?

Three tightly written sentences: what it extracts, what it returns, and how billing works. The scope statement is front-loaded and every sentence earns its place with zero filler.

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

Completeness3/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 return fields, and the billing disclosure covers the commercial behavior. What is missing is any explanation of the six inputs, four of which are undocumented anywhere, leaving a real gap for an agent trying to construct the call correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 17% and the description adds nothing about the six parameters. gl, hl, fresh, and location are entirely undocumented in both places, so an agent cannot know that gl/hl are geo-language codes or what fresh does. The description's field list describes return values, not input semantics, so it fails to compensate for the coverage gap.

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 a specific verb (Extract) and resource (Google Local Pack 3-pack and Google Places listings), scoped to 'local queries'. That is precise enough for an agent to know what it returns, though it never explicitly distinguishes itself from the sibling google_serp, which could also surface local results.

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 by the phrase 'for local queries' and the listed place-specific fields, which gives an agent a reasonable sense of when this is appropriate. However, no alternative tool is named and there are no when-not-to-use conditions or prerequisites, so the guidance is only implied rather than stated.

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

All Vera tools Inspect

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

Need Help?