AIGROW

Read an AI visibility scan

get_visibility_scan

Read-onlyIdempotent

Reads a scan check_ai_visibility started in the last hour, found by the same website, city and category: the result when it is done, or how many answers are in so far. Waits up to forty seconds for a running scan. Starts 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": {
      "website": "<website>"
    },
    "name": "get_visibility_scan"
  }
}

Input Schema

Name	Required	Description
`city`	No	The city or area the business serves, if the website may not say.
`name`	No	The business name, if known.
`website`	Yes	The business's website address, for example bakery-example.com.
`category`	No	What the business is, for example "dentist" or "CRM software".
`language`	No	The language to answer in, as an ISO 639-1 code: en, de, fr, es, pt, it, nl, pl, sv, da or no. Any other code answers in English.

Output Schema

Name	Required	Description
`host`	No
`score`	No	Out of 100; null when the scan was cut short.
`reason`	No	Why a scan was refused.
`report`	No	The full report on aigrow.gg.
`status`	Yes	done: the result is here. running: read it with get_visibility_scan.
`answers`	No	While running: the answers in so far.
`scanned`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world, so the bar is lower, yet the description adds real behavior: a blocking wait of up to forty seconds and the possibility of a partial response ("how many answers are in so far"). The one-hour recency window is also disclosed rather than left to surprise. It does not say what happens on timeout.

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?

Two sentences with the identifying behavior and the wait disclosure front-loaded, closed by the terse "Starts nothing." The opening sentence is dense but every clause earns its place; nothing is repeated from the schema or annotations.

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?

An output schema exists, so return values need no explanation, and the description still covers the things that matter for correct invocation: matching key, recency limit, blocking wait, and partial-state results. Only timeout/error behavior is left unstated.

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, but the description adds meaning the schema cannot: website, city and category act together as a lookup key identifying which scan to read, not merely as filters. That reframes how the agent should populate the optional city/category fields.

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 ("Reads a scan") and ties it directly to the sibling that creates it ("check_ai_visibility started"), so an agent can tell read from start without opening either schema. It also says what the read yields: the finished result or the count of answers so far.

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?

"Starts nothing" explicitly routes the agent to check_ai_visibility for initiating a scan and frames this as a follow-up/polling call. It also bounds applicability to scans from the last hour matched by website, city and category. It stops short of saying what to do when no matching scan exists.

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

All AIGROW 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?