TofuBofu AI Visibility

get_visibility_report

Read-only

Fetch the results of an AI-visibility scan started with scan_ai_visibility.

Args:
    report_id: The id returned by scan_ai_visibility.

Returns:
    While running: {status: "running", progress}. When done: the Tofu Index
    (named in the consideration set) and the Bofu Index (picked head to
    head), each with its fraction, the Tofu Index per engine, share of
    voice, sentiment, the top competitors winning the answers, any gap
    between the competitors the user named and the ones AI names, and
    top_fixes, the open items at the top of the brand's Fixes list (the same
    list the app's Fixes page shows; empty when there is none), plus the
    report_url.

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": {
      "report_id": "<report_id>"
    },
    "name": "get_visibility_report"
  }
}

Input Schema

Name	Required	Description	Default
`report_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 16, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds the crucial behavioral fact that the call is asynchronous and may return a running state with progress before a completed result. It also enumerates what the completed payload contains (Tofu/Bofu Index, per-engine breakdown, share of voice, sentiment, competitors, gap analysis, top_fixes, report_url), which is exactly the context annotations cannot supply.

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?

The purpose sentence is front-loaded and the Args/Returns structure is scannable. The Returns block is long, but since there is no output schema it largely earns its space; the nested parenthetical about the Fixes list is slightly verbose.

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?

With no output schema, the description carries the full burden of describing the response, and it does so thoroughly, including the intermediate running state and the optional/empty case for top_fixes. Nothing essential for correct invocation is missing.

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 0% and the single parameter is just typed 'string', so the description must compensate — and it does by telling the agent the report_id is the value returned by scan_ai_visibility, which is the only semantic fact needed. It stops short of specifying format or behavior for an invalid/expired id.

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 ('Fetch the results of an AI-visibility scan') and ties it directly to the sibling that creates the scan, so an agent can tell it apart from scan_ai_visibility without opening a schema. The distinction between starting a scan and retrieving its results is unambiguous.

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?

The description establishes the prerequisite workflow clearly: this is called with the id returned by scan_ai_visibility, i.e. after a scan has been started. It does not state exclusions or what to do instead if no scan exists, but the sequencing guidance is explicit.

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

All TofuBofu AI Visibility 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?