Skip to main content
Glama

run_agentic_readiness_audit

Read-only

Free top-of-funnel scan: could a buyer agent find and buy this publisher? Checks adagents.json, standardized taxonomy tagging, audience segments in a readable schema, and a product/deals catalog. Returns what a buyer agent would see and what it cannot.

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

Input Schema

NameRequiredDescriptionDefault
domainYesPublisher domain, for example example.com.
outputFormatNomarkdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavioral context: the scan is free (cost disclosure) and it reports negative findings ('what it cannot'), which tells the agent the output includes gaps, not just successes. It omits latency, rate limits, and failure behavior for unreachable domains.

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?

Two tight sentences with zero waste. The value proposition and scope come first, the concrete checks are listed next, and the return semantics close it out — properly front-loaded.

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 two-parameter read-only scan with no output schema, the description tells the agent what is inspected and qualitatively what comes back. What remains thin is how results are shaped and how outputFormat changes them, but that is minor at this complexity.

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 50%: 'domain' is documented in the schema, while 'outputFormat' carries only an enum plus a markdown default. The description adds no parameter-level meaning at all, but the enum and default make outputFormat largely self-explanatory, so the baseline 3 applies rather than a penalty.

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?

States a specific verb and resource ('scan' the publisher's agentic readiness) and enumerates the four concrete things inspected: adagents.json, taxonomy tagging, audience segments, and product/deals catalog. The 'buyer agent' framing is distinctive, but it never explicitly contrasts with the nearby run_publisher_revenue_audit or check_crawler_blocks siblings, so an agent must infer the boundary.

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?

'Free top-of-funnel scan' implies this is an early, low-cost triage step rather than a deep audit, which gives implied usage context. However there is no explicit when-to-use/when-not statement, no mention of the closest alternative (run_publisher_revenue_audit), and no stated prerequisites such as the domain needing to be live.

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