Skip to main content
Glama
ap-agent MCP server

ap-agent MCP server

by Icandi40

get_audit_trail

Read-only

Retrieve every audit log entry for a proposal and its underlying invoice to trace approval and payment history.

Instructions

Every audit log entry for a proposal and the invoice behind it.

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": {
      "proposal_id": "<proposal_id>"
    },
    "name": "get_audit_trail"
  }
}

Input Schema

NameRequiredDescriptionDefault
proposal_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful scope information — that results span both the proposal and the invoice behind it — but says nothing about ordering, completeness limits, or retention, which matter for an audit trail.

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?

One short sentence with no padding, and the resource scope is front-loaded. The trailing 'and the invoice behind it' is slightly loose phrasing but carries real scope information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 shape need not be described, and the read-only annotation covers safety. Still, for an audit tool the description does not address whether all entries are returned, how they are ordered, or what happens for proposals without invoices — gaps an agent would care about.

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 description coverage is 0% for the single proposal_id parameter, so the schema gives only a type. The description implicitly ties the input to a proposal, which partially compensates, but it does not state the expected identifier format or behavior when the proposal has no linked invoice.

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 the specific resource it returns (audit log entries) and scopes it to a proposal plus its backing invoice, which clearly separates it from siblings like get_proposal or check_invoice. It lacks an explicit verb ('returns'/'lists'), but the noun phrase is unambiguous about what the tool yields.

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 statement of when to call this versus get_proposal, check_invoice, or the list_* tools, and no mention of preconditions or exclusions. The agent must infer that this is the forensic/history view rather than the current-state view.

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