Skip to main content
Glama

Skillshop

audit_status_report

Check a status update before it goes to a person: flags completion claims with no evidence, hedged results, and missing blockers (paid, metered; pairs with the free honest-status skill).

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": {
      "report": "<report>"
    },
    "name": "audit_status_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
reportYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It usefully discloses that the tool flags rather than rewrites, and that it is paid/metered while the paired skill is free — cost and mutability signals an agent needs. However, it does not state whether the input is analyzed verbatim, whether findings are ranked, or whether any severity/blocking semantics apply, which are material for a review tool.

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?

One sentence, front-loaded with the action and timing, then the detection categories, then the operational note about metering and pairing. No filler or redundant restatement of the tool name.

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?

An output schema exists, so return-value explanation is not required, and the tool is structurally simple with one required string. The description supplies purpose, timing, detection scope, and cost model. What remains thin is input-format expectation, a minor gap for this complexity level.

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?

The single parameter 'report' has 0% schema description coverage, so the description must compensate. It does imply the parameter is the status update text bound for a recipient, which is real added meaning. It does not specify expected format (plain text, markdown, pasted message) or length expectations, leaving a gap for a 1-param, fully-required tool.

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 action (checking/auditing a status update) and enumerates the concrete defect classes it detects: unsupported completion claims, hedged results, missing blockers. That is far more informative than the bare name, and the resource ('status update before it goes to a person') cleanly separates it from sibling audits like audit_backup_plan or audit_grant_budget. It stops short of an explicit 'not for X' contrast, which keeps it at 4 rather than 5.

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?

The phrase 'before it goes to a person' gives a clear invocation moment: pre-send review of a status update. It also points to a companion resource ('pairs with the free honest-status skill'), which helps the agent route. There is no explicit exclusion or when-not guidance, so it is a 4 rather than the top band.

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