Skip to main content
Glama

GMPSignal Real-Time Intelligence MCP (59 Tools)

google_maps_places_emails_all_in_one

Read-onlyIdempotent

Local Places & Business Leads All-in-One (Free Email + MX): Real-time structured data extraction feed for Local Places & Business Leads All-in-One (Free Email + MX).

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

Input Schema

NameRequiredDescriptionDefault
maxResultsNoMaximum number of records to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / maxResults / description
      Previous value: -"Maximum number of structured items to extract."New value: +"Maximum number of records to return."
  2. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -true
  3. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +true
  4. Added

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds essentially nothing beyond them — 'real-time' and 'Free Email + MX' are unquantified claims with no detail on source coverage, pagination, rate limits, result fields, or what a 'record' contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but the single sentence is near-zero information density: it repeats the tool name and the annotation title verbatim with no front-loaded explanation of purpose or scope. Brevity here reflects under-specification rather than efficiency.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema and no explanation of result shape, so the description should describe what a lead record includes (place fields, emails, MX status) — it does not. For a data-extraction feed with an open-world annotation, an agent cannot tell what it will get back or how it differs from other scraper siblings.

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% for the single maxResults parameter (default 10), so the schema carries the parameter meaning entirely and the description offers no additional semantics. With full coverage and no compensating detail needed, baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The sentence is circular: 'Real-time structured data extraction feed for Local Places & Business Leads All-in-One (Free Email + MX)' restates the tool name and annotation title rather than defining the operation. The only extra signal is embedded in the marketing parenthetical ('Free Email + MX'), which hints at email/MX-record enrichment but never states what the tool actually does or returns.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no routing to alternatives such as google_serp_search_results_all_in_one or b2b_leads_finder_verified_emails, even though those siblings plausibly overlap. The phrase 'Local Places & Business Leads' implies a domain but not a selection condition.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources