Skip to main content
Glama

Visibility Genies

Get a local rank grid

get_local_rank_grid

Runs one Google Maps search for every point of a square grid centred on a coordinate and reports where the target business ranks at each point, with each point's result count and top listing. Use it to see how Maps visibility changes across an area. Looks 20 results deep per point. Estimated price: $0.04 for 3x3 (9 searches), $0.10 for 5x5 (25 searches). A grid bought with a cid opens on the Local page's Maps visibility tab. Each call may spend up to the workspace's agent spend limit ($2.00 unless changed in Settings) without asking: it holds at most its estimate plus a margin while it runs and is charged what it bought, never more. A call whose maximum is above the limit is refused before anything is bought, with its estimate and maximum: ask the user, then call again with approvedMaxCostUsd set to the amount they approved.

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": {
      "projectId": "<projectId>",
      "keyword": "<keyword>",
      "target": "<target>",
      "center": "<center>"
    },
    "name": "get_local_rank_grid"
  }
}

Input Schema

NameRequiredDescriptionDefault
zoomNoMaps zoom for each search. Worked out from spacingKm and the latitude when left out.
centerYesCoordinate at the middle of the grid.
deviceNoDevice to search as. Default mobile.
targetYesThe business to find. Rows are matched by cid (most reliable), then place_id, then a title that contains the text, ignoring case. name is used only when cid and placeId do not match. Give at least one.
keywordYesKeyword to search on Maps.
gridSizeNoPoints per side. 3 runs 9 searches (default), 5 runs 25.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
spacingKmNoDistance between neighbouring points in km. Default 2.
languageCodeNoLanguage of the searches. Defaults to the project's.
approvedMaxCostUsdNoThe most, in USD, the user approved for this call after seeing its estimate and maximum. Only needed after a call was refused for costing more than the workspace's agent spend limit; never set it without asking the user.

Output Schema

NameRequiredDescriptionDefault
costNo
gridYes
metaNo
summaryYes
savedResultIdNo
matchedBusinessYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false) by disclosing that each call spends real money, publishes per-grid-size price estimates, states the default $2.00 agent spend limit, explains that funds are held at estimate plus margin but charged only for what was bought, and describes the pre-purchase refusal and approvedMaxCostUsd retry flow. That is exactly the kind of billing and refusal behavior an agent cannot infer from 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?

Front-loaded with the core action and the practical usage note, then the cost mechanics. Slightly wordy in the spend-hold sentence ("holds at most its estimate plus a margin while it runs and is charged what it bought, never more"), but every part carries information the agent needs before a paid call.

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?

For a 10-parameter, paid, open-world tool with a nested target object, the description covers purpose, cost, refusal handling, and output destination, and an output schema already covers return shape. Nothing material is missing for correct invocation.

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 baseline is 3, but the description adds real meaning: it ties gridSize to search count and cost (9 vs 25 searches, $0.04 vs $0.10) and explains the approvedMaxCostUsd contract as the post-refusal approval amount. Other parameters such as zoom, spacingKm and target matching are left to the schema, which documents them adequately.

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: runs one Google Maps search per point of a square grid centred on a coordinate and reports where the target business ranks, plus result count and top listing per point. The grid/area scope is concrete enough to distinguish it from a single-SERP tool like get_local_serp_results or a continuous rank tracker.

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?

"Use it to see how Maps visibility changes across an area" gives a clear selection context, and the note that a cid-bought grid opens on the Local page's Maps visibility tab tells the agent where the output lands. It does not explicitly say when to prefer a single SERP lookup or a rank tracker instead, so alternatives are left implicit.

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