Radar noEixo

Search google places

search_google_places

Read-only

🗺️ GARIMPO LEADS — Busca estabelecimentos no Google Maps (como o botão "Google Maps" da tela) e devolve uma PRÉVIA: nome, telefone, site, endereço, avaliação. Não grava nada — para salvar, mande os escolhidos em add_domain_checker_leads com um list_name. Usa a chave Google Places da conta (gera custo): até 5 cidades × 5 tipos por chamada.

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": {
      "cidades": "<cidades>",
      "tipos": "<tipos>"
    },
    "name": "search_google_places"
  }
}

Input Schema

Name	Required	Description
`tipos`	Yes	Tipos de negócio, array JSON ou separados por vírgula (ex.: "clínica odontológica, consultório")
`cidades`	Yes	Cidades, array JSON ou separadas por vírgula (ex.: "Florianópolis SC, Joinville SC")
`min_rating`	No	Nota mínima no Google (padrão 4.0)
`min_reviews`	No	Mínimo de avaliações (padrão 5)
`target_user_id`	No	(Só o admin da plataforma) userId da conta a operar

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 26, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, but the description adds real context beyond them: it uses the account's Google Places key and therefore incurs cost, and it caps the workload at 'até 5 cidades × 5 tipos por chamada'. It also restates the no-write behavior in plain terms and previews the return fields.

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 compact clauses ordered by importance: what it does and returns, that it does not persist plus the save path, then the cost/quota caveat. No filler; every sentence carries distinct information.

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

Completeness5/5

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

Despite no output schema, the description lists the return fields, discloses the cost model, the per-call limits, and the follow-up tool for persistence. An agent has everything needed to decide to call it and to handle the result correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description earns extra credit by disclosing the 'até 5 cidades × 5 tipos' limit, which directly constrains the two required parameters (cidades and tipos) in a way the schema does not. It adds nothing about min_rating/min_reviews/target_user_id, but those are already documented in 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?

States a specific verb and resource ('Busca estabelecimentos no Google Maps') and enumerates what is returned (nome, telefone, site, endereço, avaliação). It is clearly distinguished from the adjacent write-path sibling by naming add_domain_checker_leads as the tool that persists results.

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 explicit when-to-use ('como o botão Google Maps da tela'), an explicit non-goal ('Não grava nada'), and the alternative to use for saving ('mande os escolhidos em add_domain_checker_leads com um list_name'). The agent does not need to infer the search-then-save workflow.

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

All Radar noEixo 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?