Skip to main content
Glama
Sign In

Rankwise

by com.tryrankwise
OverviewDiscussionsAdmin

Score AI visibility readiness

score_ai_visibility
Read-onlyIdempotent

Score how ready a website's homepage is to be found and cited by AI search engines (crawler access, structured data, content signals). Returns a score, issues and quick wins. This is an on-page readiness check, not a measurement of real AI citations. Called without signing in, the result also carries a claim link: give it to the person who runs the site, and one sign-in opens a Rankwise workspace with that domain already added, ready once they start the 3-day free trial. A claim link works once and expires after 72 hours.

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": "score_ai_visibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesThe domain to score, e.g. example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior. The description adds valuable context beyond that: it describes the returned score/issues/quick wins, the claim-link produced for anonymous calls, the single-use 72-hour expiry, and the sign-in/free-trial flow.

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?

The description is front-loaded with purpose, then return contents, then claim-link behavior. The claim-link details are somewhat long but operationally relevant to what the agent must communicate, and no sentence is filler.

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, what is checked, what is returned, the key limitation versus citation measurement, and the claim-link lifecycle. 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.

Parameters3/5

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

There is one required domain parameter and schema description coverage is 100%, so the schema already explains the expected format via 'e.g. example.com'. The description adds no further parameter constraints or syntax beyond what the schema provides, making the baseline 3 appropriate.

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 ('Score') and resource ('a website's homepage') and lists the readiness dimensions checked (crawler access, structured data, content signals). It also explicitly distinguishes itself from real citation measurement, which separates it from siblings like run_citation_check.

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 makes clear this is an on-page readiness check and not a measurement of real AI citations, giving the agent a useful usage boundary. However, it does not explicitly route the agent to narrower alternatives such as check_ai_crawler_access or check_citation_readiness.

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

All Rankwise 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