Skip to main content
Glama
Sign In

CallAI SEO

by com.callaiapi
OverviewDiscussionsAdmin

Read a domain check

domain_check_results
Read-only

Progress and per-domain verdicts of a check started with domain_check_start: verdict, reason, first archive year, stable years, Baidu results, referring domains and spam score. A check can take minutes; rows stay pending until their steps finish. Reading is free.

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": {
      "check_id": "<check_id>"
    },
    "name": "domain_check_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNoThe "next" value of the previous page.
limitNoRows per page, up to 200 (default 50).
verdictNoOnly rows with this verdict.
check_idYesThe id from domain_check_start.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Beyond readOnlyHint/openWorldHint it discloses genuinely useful behavior: the operation is asynchronous and long-running, rows can be pending, and 'Reading is free' signals no credit cost. It stops short of describing the pagination envelope or any rate/refresh guidance, but it meaningfully extends the annotations.

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 statement is front-loaded and the follow-up sentences on latency and cost each earn their place. The middle field-enumeration sentence is a long run-on that could be tightened, but it carries real information given there is no output schema.

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 no output schema, the description usefully enumerates the per-row verdict fields, and it explains the async/pending lifecycle that an agent must handle. The only gap is the paging model (after/limit/next) which the description never mentions, leaving the agent to infer polling mechanics from the schema alone.

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 coverage is 100%, so after, limit, verdict, and check_id are already fully documented in the schema. The description adds no filtering, paging, or enum semantics beyond what is structured, which is the baseline 3 case.

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?

The description names a specific verb and resource ('Progress and per-domain verdicts of a check') and ties it to the sibling that produces the input ('a check started with domain_check_start'). An agent can immediately separate this read tool from domain_check_start without inspecting 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear context for when to call: after domain_check_start, with the expectation that results may be incomplete and that polling is normal ('rows stay pending until their steps finish'). It doesn't state explicit when-not conditions or name alternatives, but for a results-reader there are no real competing siblings.

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

All CallAI SEO 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