Skip to main content
Glama

audit-terms

Terms-of-service and privacy-policy audit kit. The complete weighted audit methodology: a seven-category rubric with anchored 0-10 scoring, penalty and bonus flags, a weighted total with letter grade, and a plain-English verdict. One call returns the full kit; the buyer's agent audits the document itself with its own tools. Price: $12.00 per call, paid in USDC on Base mainnet over x402; an unpaid call answers HTTP 402 with the exact machine-readable payment terms.

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": {
      "url": "<url>"
    },
    "name": "audit-terms"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe terms-of-service or privacy-policy page the buyer's agent audits with the kit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does substantial work: it discloses the price ($12.00 per call), the payment rail (USDC on Base mainnet via x402), and the exact failure mode (unpaid calls return HTTP 402 with machine-readable payment terms). What is missing is whether the URL is fetched or merely recorded, and whether repeated calls incur repeated charges — meaningful for a paid tool.

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?

The purpose is front-loaded in the first sentence and the payment terms are placed last, which is the right ordering. The middle enumeration of rubric components is dense but each item is informative; a little marketing register ('complete weighted audit methodology') could be trimmed.

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, so the description must describe the return payload, and it does so concretely by listing rubric, scoring anchors, flags, weighted total, grade, and verdict. The pricing and 402 behavior round out the commercial context. The remaining hole is the role of the url parameter for a kit-style return.

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 there is only one parameter, so the baseline of 3 applies; the description's phrase 'the page the buyer's agent audits with the kit' largely restates the schema's own wording. Given that the tool returns a methodology kit rather than an analysis, the description leaves genuinely unclear what the URL is actually used for.

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?

Specific verb-and-resource framing: it names the domain (terms-of-service and privacy-policy audit) and enumerates what one call returns (seven-category rubric, anchored 0-10 scoring, penalty/bonus flags, weighted total with letter grade, verdict). It also explicitly distinguishes itself from the audit itself by stating the buyer's agent performs the audit with its own tools. It loses a point because the name 'audit-terms' suggests it audits a document, while the body says it returns a kit — the reader has to reconcile that.

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?

There is a real usage signal in 'One call returns the full kit; the buyer's agent audits the document itself with its own tools', which tells the caller this is a one-shot retrieval and not a per-page analysis loop. However, it never states when to pick this over a related tool, nor any when-not conditions or prerequisites beyond the payment note.

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