Skip to main content
Glama

Your sealed audits (Record plan)

list_audits
Read-onlyIdempotent

Lists the compliance and underwriting audits made for the signed-in Record account, each with its period, when it was made, and its SHA-256 fingerprint, with the link to download them on provkeep.com.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds real value beyond them by disclosing what each returned item contains (period, creation timestamp, SHA-256 fingerprint) and that a download link on provkeep.com is included. It omits ordering, result limits, and what happens for accounts without the Record plan, which keeps it below a 5.

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?

Everything is packed into a single front-loaded sentence with no filler; each clause (scope, fields, fingerprint, download link) carries information. It is slightly run-on and could be split for readability, but no sentence is wasted.

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?

With no input parameters and no output schema, the description must carry the return-value burden, and it does describe the shape of each item plus how to retrieve the actual files. Minor gaps remain around pagination, ordering, and plan-gated failure behavior, but for a simple zero-argument list tool this is close to sufficient.

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 takes zero parameters, so there is no parameter meaning to convey; the schema is fully closed and the description correctly describes a no-argument listing operation. Per the zero-parameter baseline this lands at 4, with no gaps to compensate 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?

The description names a specific verb and resource ('Lists the compliance and underwriting audits') and scopes it to 'the signed-in Record account', plus enumerates the fields it returns (period, creation date, SHA-256 fingerprint, download link). It is unambiguous what the tool does, though it does not explicitly contrast itself with the other list_* siblings, which the distinctive 'audits' resource makes largely unnecessary.

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?

Usage is only implied: the tool returns audits for the signed-in account, and the title hints at a 'Record plan' requirement, but the description never states prerequisites, plan gating, or when to use this versus other listing tools such as list_changes. An agent can infer the use case but gets no explicit when/when-not guidance.

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