Skip to main content
Glama

Hunter Pūteanui (hcIfU)

audit_agent_endpoint

Read-onlyIdempotent

Audit a domain for /.well-known/mcp.json, /.well-known/x402, and /llms.txt conformance.

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

Input Schema

NameRequiredDescriptionDefault
urlNoOptional URL to extract into clean Markdown
formatNojson_bundle or zip_base64json_bundle
base_urlNoOptional domain to audit for MCP & x402 conformance
workloadNocoding, search, or generalcoding
tools_csvNoOptional comma-separated tool names for FastMCP scaffoldping,fetch_summary
html_inputNoOptional raw HTML to extract into clean Markdown
amount_usdcNoPay what you can afford in USDC (minimum 0.01 — e.g. 0.01, 0.10, 2.00, 100.00). Every amount receives the full package.
descriptionNoOptional custom FastMCP server descriptionCustom FastMCP Server
server_nameNoOptional custom FastMCP server name to scaffoldcustom_tools

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the useful behavioral detail of exactly which well-known endpoints are probed, but says nothing about network egress expectations, what a conformance failure looks like, or the payment requirement implied by amount_usdc.

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?

A single front-loaded sentence with no filler, and the probed paths are placed immediately after the verb. It is efficient but so terse relative to a 9-parameter, multi-mode tool that brevity shades into under-specification.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 9 optional parameters spanning auditing, HTML-to-Markdown extraction, scaffold generation, and payment, plus no output schema, the definition needs to explain how these modes interact and what a successful audit returns. One sentence covering only the audit mode leaves an agent unable to decide which parameters to populate or what to expect back.

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 description coverage is 100%, so the baseline of 3 applies; every parameter including amount_usdc's 'pay what you can afford' note is documented inline. The description contributes nothing beyond the schema, and in particular does not explain how the audit-related base_url relates to the extraction and scaffolding parameters that share the same call.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (audit) and the exact resources probed (/.well-known/mcp.json, /.well-known/x402, /llms.txt), which is concrete. However, the schema exposes clearly unrelated capabilities — HTML extraction (url, html_input), FastMCP scaffolding (server_name, tools_csv, workload), and USDC payment (amount_usdc) — none of which the description acknowledges, so the stated purpose covers only a fraction of what the tool apparently does.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no routing to alternatives. The agent is not told, for example, to prefer extract_webpage_markdown for extraction or generate_fastmcp_scaffold for scaffolding, nor when base_url versus url should be supplied.

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