Skip to main content
Glama

check_agent_readiness

Read-onlyIdempotent

Free on testnet. Automated scan, not human-verified. Scan-only quick read of whether AI agents can discover and buy from a website. Returns the engine's report as-is: scanner_version and scan_id ("v6"), report.score (scan-only), report.band (can be 'Partly assessed'), report.coverage, report.summary, report.confidence, report.can_agents_buy, report.who_eats_the_loss (display label "Who carries the risk?"; needs the 5 answers, so not assessed here), report.archetype ('unclassified' if not classified), report.rows (with unknown_reason), report.gaps, report.actions (always exactly 3: 2 business then 1 technical, each with kind "business" | "technical"), report.ledger (related Ledger entries), checks, evidence, findings, chatgpt_wallet (ChatGPT Wallet and cloud browser rules from OpenAI's public merchant guides: each rule is MATCH, NOT_MATCH or UNKNOWN with why, fix steps and the OpenAI source; UNKNOWN means it cannot be seen from outside; possible_block marks a block seen by our unsigned request, not proof; it does not change the score), and scan_interrupted.reason (timeout|blocked|dns_tls|robots_disallowed|refused|http_error) when the scan could not finish. Input: a bare domain (e.g. "yourstore.com"). It reads public pages only; it is NOT a certification, audit or legal advice. Open questions only the business can answer come back with a link to https://thepaymentsnotes.com/readiness. Limits: 3 scans per caller per day and 50 per day overall, shared with the website; results are cached for 24h. Weekly newsletter: https://thepaymentstack.substack.com

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

Input Schema

NameRequiredDescriptionDefault
domainYesBare domain only, e.g. 'yourstore.com' (no https://, path or port)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the readOnly/openWorld/idempotent annotations, it discloses rate limits, shared quota, 24h caching, that results are cached and unverified, and enumerates scan_interrupted reasons (timeout|blocked|dns_tls|robots_disallowed|refused|http_error). It also clarifies that possible_block is not proof and does not change the score, and that some fields (e.g. who_eats_the_loss) are deliberately not assessed here.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The key framing (free, automated, scan-only, not a certification) is front-loaded, but the middle is one enormous run-on sentence enumerating a dozen-plus return fields. The trailing newsletter/Substack links do not help an agent invoke the tool and dilute the payload.

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?

With no output schema, the field-by-field description of report.*, checks, evidence, findings and chatgpt_wallet is necessary and present, along with interruption handling, quota limits, and explicit caveats about what the scan cannot prove. An agent has enough to call it and interpret the result.

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% and the single domain parameter is fully documented in the schema, so the description adds only the example 'yourstore.com' and the 'bare domain' emphasis. This is the baseline 3 case where the schema does the heavy lifting.

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 states a specific verb and resource: a 'scan-only quick read of whether AI agents can discover and buy from a website,' and scopes it with 'reads public pages only' and 'NOT a certification, audit or legal advice.' It is clearly distinct from ledger/status siblings, though it never explicitly names an alternative tool for comparison.

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 'Input: a bare domain' and the free-on-testnet framing, and the limits (3 per caller per day, 50/day shared, 24h cache) tell the agent when a call will fail. However, there is no explicit 'use this when X, use that when Y' routing and no guidance on what to do with open questions beyond a link.

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