Skip to main content
Glama
Sign In

Squish

by co.squish
OverviewDiscussionsAdmin

Run my ai visibility report

run_my_ai_visibility_report

Runs an AI Visibility report on one of the customer's OWN Squish-hosted sites and SAVES it to their history, so the grade can be tracked over time (the CRM shows it move). Use this — not check_ai_visibility — when a signed-in customer asks to check or re-check THEIR OWN site, or after applying fixes to record the new grade. The domain must be one of the customer's own hosted sites. Returns the same graded result as check_ai_visibility ({ grade, score, findings, ... }), and the result is recorded against their account. Read-only to the site (it just scans).

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": {
      "domain": "<domain>"
    },
    "name": "run_my_ai_visibility_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesThe customer's own hosted site to report on (their domain).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false and destructiveHint=false; the description adds the crucial context that the write is a history record, not a site mutation ('Read-only to the site (it just scans)'), and that the result is recorded against the account so the grade can be tracked over time. It also discloses the return shape, which matters since no output schema exists. This is consistent with, not contradictory to, the non-read-only annotation.

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 key distinction from check_ai_visibility and the persistence side effect are front-loaded, and every sentence carries information. It is slightly dense with parentheticals and repeated emphasis on 'OWN', which costs a little tightness but not clarity.

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 one-parameter tool with no output schema, the description covers purpose, eligibility, side effects, return shape, and the sibling alternative. Nothing an agent needs in order to call it correctly 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 100% and the single parameter is already documented, so the schema carries most of the load. The description still adds a meaningful constraint beyond the schema: the domain must be one of the customer's own hosted sites, which is an eligibility rule rather than a format detail.

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 an AI Visibility report on one of the customer's OWN Squish-hosted sites') plus the side effect ('SAVES it to their history'). It explicitly names the sibling it is not (check_ai_visibility), so an agent can route between the two without opening either schema.

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 conditions: a signed-in customer asking to check or re-check their OWN site, or after applying fixes to record the new grade. It also names the alternative tool and the constraint (domain must be one of the customer's own hosted sites), leaving little to inference.

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

All Squish toolsInspect
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