Chinng AI-Agent Portal

portal_get_agent_surface

Fetch one website's full Agent-Readiness assessment by domain.

Args: domain: the site's domain (e.g. "example.com"). Normalized (scheme/path/case stripped).

Returns: domain, score (0-100 overall), level, level_label, categories[] (per-category pct with passed/failed/neutral check ids), checks[] (every verified check with its HTTP status and byte size), llms_txt_url / llms_full_txt_url, discovered_via and first_seen_at / checked_at / updated_at timestamps. Returns {error: "not_found", domain} if the domain has not been scanned.

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

Input Schema

Name	Required	Description	Default
`domain`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A4.1/5.0

Behavior4/5

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

No annotations are supplied, so the description carries the burden, and it does disclose normalization of the domain input, the full return shape, and the specific not_found error behavior. It does not mention auth, rate limits, or whether a missing scan triggers a scan.

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?

Front-loaded one-line purpose followed by clearly labeled Args/Returns; the Returns block is long but enumerates fields that no output schema is exposed for in the text, so it largely earns its space.

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?

For a single-parameter read tool, the definition covers input format, error case, and return contents thoroughly. The only meaningful gap is guidance on how this differs from the sibling list/search tools when the agent has many domains.

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% with a single bare 'domain' string, so the description's note that the domain is normalized (scheme/path/case stripped) plus an example ('example.com') adds real meaning the schema lacks.

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 one website's full Agent-Readiness assessment') plus the scoping key ('by domain'), which clearly distinguishes it from list/search siblings like portal_list_agent_surfaces and portal_search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied by 'Fetch one website's ... by domain' and the not_found return case, but there is no explicit when-to-use/when-not guidance or named alternative for listing many sites (e.g. portal_list_agent_surfaces).

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

All Chinng AI-Agent Portal 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?