Skip to main content
Glama

apex-dev

Agent card grade

agent_card_grade
Read-onlyIdempotent

Audit and grade any AI agent domain or A2A agent card (/.well-known/agent-card.json, agent.json, mcp-server-card.json, x402, /llms.txt) with a 0-100 score, A+-F grade, and concrete fixes. $0.002 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for terms, then call again with payment.

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

Input Schema

NameRequiredDescriptionDefault
domainYesPublic domain or /.well-known/agent-card.json URL to audit.
paymentNosigned x402 payment payload (PAYMENT-SIGNATURE).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive, so safety is covered; the description adds the critical non-obvious traits: this is a paid tool at $0.002/call, settlement happens over x402 in specific tokens/chains, and the first call returns terms rather than results. Remaining gaps are minor (what an unpaid or invalid-domain response looks like).

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?

Three front-loaded sentences: capability and accepted inputs, price, then call sequence. No filler, and the payment mechanics are ordered in the sequence the caller must follow.

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?

No output schema exists, and the description compensates by stating what comes back (score, grade, fixes). Pricing and the two-step payment flow are covered, so an agent can call it correctly. Only error/failure behavior on unpaid or unreachable domains is left unspecified.

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 100%, so the baseline is 3, but the description genuinely adds semantics the schema does not carry: the two-phase protocol in which `payment` is first absent and then supplied. It does not explain the payment payload format beyond the schema's own note, which keeps it at 4.

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 pair ('audit and grade') and a specific resource ('AI agent domain or A2A agent card'), and names the concrete artifact types it reads (agent-card.json, agent.json, mcp-server-card.json, x402, /llms.txt). It also states the output shape up front (0-100 score, A+-F grade, concrete fixes), making it unmistakable what the tool produces.

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 an explicit operating procedure: call once without `payment` to get terms, then call again with `payment` to get the audit. That is real when-to-use guidance an agent would otherwise get wrong. It does not differentiate against nearby catalog tools (e.g. robots_check, x402_price_comps), so it stops short of a 5.

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