Skip to main content
Glama

Chinng AI-Agent Portal

portal_list_agent_surfaces

List scanned websites by their AI-agent readiness (the Agent-Readiness directory).

A separate content family from news/CVE: each entry is a domain we actively scanned for agent-facing surfaces across five categories (Discoverability / Content / Bot Access Control / API-Auth-MCP-Skill / Commerce). Checks are graded like the Cloudflare Agent-Ready scanner: each category yields a percentage, and the overall score (0-100, Commerce excluded as informational) maps to Level 0-3 (0 Unprepared / 1 Agent-Curious / 2 Agent-Aware / 3 Agent-Native). Only scanned domains with results are listed.

Args: level: filter to a single readiness level (0-3) min_score: only surfaces with overall score (0-100) >= this value discovered_via: candidate source filter. e.g. "tranco" / "majestic" / "manual" sort: "score" (default, highest readiness first) or "recent" (recently changed first, for level-up tracking) limit: number of results (default 20, max 100) offset: paging start position

Returns: {total, count, limit, offset, items[]} — each item has domain, score (0-100), level, level_label, categories[] (per-category pct + pass/fail breakdown), checks[] (every check with its HTTP status), llms_txt_url, discovered_via and timestamps.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "portal_list_agent_surfaces"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoscore
levelNo
limitNo
offsetNo
min_scoreNo
discovered_viaNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it explains the grading model (per-category percentages, overall 0-100 with Commerce excluded as informational, mapped to Level 0-3), states the population constraint ("Only scanned domains with results are listed"), and caps limit at 100. It stops short of stating auth requirements, rate limits, or freshness/latency of the scan data.

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 with the purpose and family distinction, then cleanly sectioned into Args and Returns. The Cloudflare scanner analogy and the five enumerated category names are informative but consume space that a leaner definition could compress; nothing is outright waste.

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 six-parameter paginated list tool with no annotation coverage, the definition covers filtering, sorting, paging, the scoring model, and the population rule an agent needs to interpret empty results. The Returns block overlaps the output schema but adds the level_label semantics, so it reinforces rather than pads.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

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

Schema description coverage is 0%, so the description must do all the work, and it does: level bounded to 0-3, min_score as a 0-100 threshold, discovered_via with concrete examples ("tranco" / "majestic" / "manual"), sort enumerated with default and the meaning of each value, and limit/offset with default 20, max 100, and paging semantics.

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?

Opens with a specific verb and resource ("List scanned websites by their AI-agent readiness") and immediately distinguishes the content family: "A separate content family from news/CVE." That contrast plus the named directory scope lets an agent separate this from portal_list, portal_list_government, and portal_search without opening any 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?

Gives clear operating context: only scanned domains with results are listed, level 0-3, min_score 0-100, and sort="recent" is explicitly framed as the mode for "level-up tracking." What it lacks is any explicit statement of when to reach for this versus portal_get_agent_surface for a single domain, or any exclusion guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources