Skip to main content
Glama

audit

Compares published privacy policies against code to find missing services, sections, cross-border transfer issues, and broken article references, returning evidence-backed findings for review.

Instructions

Call for a first-time or full check of the published documents against the code. Mechanically compares the code with the privacy policy (services not mentioned, required sections missing, cross-border transfer) and checks both documents for broken article references. Returns findings with evidence; candidates still need a human or AI to confirm. Requires .policy-drift.json.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does substantial work: it explains the mechanical comparison, lists example checks, says findings include evidence, notes candidates need human or AI confirmation, and states the .policy-drift.json prerequisite. It still omits whether the tool is read-only or has side effects, so it is not fully complete.

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?

The definition is compact and front-loaded: it states the action first, then the checks performed, then the return and confirmation caveat, and finally the prerequisite. Every sentence contributes useful information without repetition.

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?

Given zero parameters, no annotations, and no output schema, the description is complete enough for an agent to understand what the tool does, what it checks, what it returns conceptually, that findings require confirmation, and what file must exist. No critical invocation context is missing.

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?

The tool has zero input parameters, so the schema baseline is high. The description adds useful prerequisite context by stating that .policy-drift.json is required, which is not represented in the empty input schema.

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?

The description uses specific language: a first-time or full check of published documents against code, mechanically comparing code with the privacy policy and checking broken article references. This clearly distinguishes a full audit from narrower sibling operations such as scan_changes or get_checklist.

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?

It says to call this for a first-time or full check, which gives clear usage context. It does not explicitly name alternatives or when not to use it, but the full-check framing sufficiently implies the appropriate situation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.