Skip to main content
Glama

AI Agent Audit and Action Review

Read a previously paid agent action review

read_agent_action_review
Read-only

Retrieve an existing report using the original private request ID. This tool is read-only and creates no new purchase.

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": {
      "request_id": "<request_id>"
    },
    "name": "read_agent_action_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idYesPrivate, unique per purchase. Generate 32 random bytes and encode as unpadded base64url.

Output Schema

NameRequiredDescriptionDefault
kindYes
modelYes
summaryYes
verdictYes
evidenceYes
findingsYes
unknownsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, but the description adds a genuinely new behavioral fact beyond that: no new purchase or charge is incurred by calling it, which matters for a paid-review workflow. It does not cover failure behavior for unknown or unpaid request IDs, keeping it short of 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the action and the identifying input, then the read-only/no-purchase guarantee. Every clause carries information an agent needs before invoking the tool.

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 an output schema present and a single fully documented parameter, the description covers the essentials for a read-only retrieval tool. The only meaningful gap is behavior on invalid or non-purchased request IDs, which an agent might reasonably want to know.

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?

Schema coverage is 100% and the schema already explains the base64url format and entropy requirement, so the baseline is 3. The description adds real meaning on top by stressing the 'original' ID from the prior purchase, implying the caller must reuse the existing value rather than mint a fresh one.

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 pairs a specific verb ('Retrieve an existing report') with the resource ('agent action review') and states the key constraint that the ID must be the original private one. It implicitly separates itself from the checkout sibling by noting it 'creates no new purchase,' though it never names that sibling.

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: 'original private request ID' signals this is for reviews already purchased, and 'creates no new purchase' hints that a different tool handles acquisition. There is no explicit when-to-use/when-not-to-use statement or named alternative, leaving the agent to infer the boundary with get_agent_action_review_checkout.

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