Skip to main content
Glama

Plures

Read the audit report

get_audit_report
Read-only

Reads the developer's Plures audit: where it is, and once people are answering, how many decisions they called right, wrong, unclear or split, with the ones they disagreed with listed first. For judgment audits: right means people would be happy with it, wrong means not happy, unclear means it needs changes.

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

Input Schema

NameRequiredDescriptionDefault
audit_idNoWhich audit. Default: the account's audit

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations only cover read-only and open-world safety, so the description must carry the rest, and it does: it discloses that results include a location, tally counts, a 'split' bucket, and a specific ordering ('the ones they disagreed with listed first'). It also defines what right, wrong and unclear mean for judgment audits, which is real behavioral context rather than restatement.

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?

Two sentences, front-loaded with what is read before the tally breakdown, and the category definitions at the end earn their space. The opening clause 'where it is, and once people are answering' is slightly compressed but not wasteful.

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 output schema, the description has to explain the return shape and largely does: location, per-category counts, ordering, and category semantics. It does not cover the empty/pre-answer state in detail or mention pagination, but nothing an agent needs in order to call it correctly is missing.

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 the single optional audit_id parameter already documents its default. The description adds no syntax, format or selection guidance beyond what the schema provides, so the baseline 3 is appropriate.

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: it reads a Plures audit and reports its location plus aggregated decision tallies. An agent can tell roughly what it returns, though 'Plures audit' is in-house jargon and no sibling (e.g. get_scorecard, audit_my_agent) is named as a contrast point.

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 explicit when-to-use or when-not-to-use guidance and no named alternative. The phrase 'once people are answering' hints at a lifecycle stage, but it does not tell an agent whether to reach for get_scorecard, get_human_answer or this tool first.

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.