Ranksmile

Site audit

audit__overview

Read-onlyIdempotent

The last site crawl for this workspace: site health and AI-search health (0-100), pages crawled, error and warning counts, and each issue with how many pages it affects, most severe first. Reads the stored crawl; 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": {
      "workspace_id": "<workspace_id>"
    },
    "name": "audit__overview"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Max rows, 1-100 (default 20).
`offset`	No	Rows to skip (default 0). Keep paging while has_more is true.
`workspace_id`	Yes	From workspace__list.

Output Schema

Name	Required	Description
`domain`	Yes
`errors`	No
`issues`	Yes	id, title, severity (error\|warning\|notice), count (pages affected), ai_search.
`has_data`	Yes
`has_more`	Yes
`warnings`	No
`updated_at`	No
`site_health`	No
`workspace_id`	Yes
`pages_crawled`	No
`pages_by_status`	No	Crawled pages per bucket: healthy, broken (no answer or 4xx/5xx), haveIssues, redirects, blocked.
`ai_search_health`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new behavioral context: it returns the most recent stored crawl only, orders issues most-severe-first, and never initiates a crawl. It omits freshness/staleness semantics for 'last crawl' and any size/rate caveats.

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?

Two sentences, front-loaded with the resource and its returned content, followed by the crucial 'starts nothing' caveat. No filler or redundancy.

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?

With an output schema covering return shape, 100% parameter coverage, and annotations covering safety, the description supplies the remaining essentials: scope (last stored crawl), ordering, and non-triggering behavior. Pagination is only implied via the schema's 'has_more' note, a minor gap.

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?

Schema description coverage is 100%, so limit, offset, and workspace_id are fully documented in the schema. The description adds no parameter-level meaning beyond that, making the baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the specific resource ('the last site crawl for this workspace') and enumerates what it returns: health scores, crawl counts, and per-issue affected-page counts. That clearly separates it from visibility__overview and the ranking tools, though it never names a sibling explicitly, which keeps it short of a 5.

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?

'Reads the stored crawl; starts nothing' gives the agent a clear usage boundary — call this to inspect existing audit data, not to trigger a crawl. It does not name an alternative tool for starting a crawl or for other health views, so it stops at clear context rather than full routing guidance.

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

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