Skip to main content
Glama

Audit trail

get_audit_trail

Hash-chained audit events for an envelope, oldest first.

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

Input Schema

NameRequiredDescriptionDefault
api_keyNoDocuflex API key (dfx_live_...). Optional if sent as the x-docuflex-api-key header.
account_idNoDocuflex account id. Optional if sent as x-docuflex-account or if the key belongs to exactly one account.
envelope_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It does disclose two meaningful traits beyond a bare name: events are hash-chained (tamper-evident, each entry linked to the prior one) and returned oldest first. It says nothing about volume, pagination, truncation, or whether the full history is always returned, which matters for a potentially long log.

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?

A single front-loaded sentence with no filler. The scoping ('for an envelope') and the ordering ('oldest first') are both stated compactly.

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?

For a read-only lookup with no output schema and no annotations, the definition is merely adequate. An agent still cannot tell whether the response is paginated, capped, or complete, which is the main open question for an audit-log endpoint.

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 67%; api_key and account_id are documented in the schema with their header alternatives, while the required envelope_id has no schema description. The description only implies that envelope_id identifies the envelope whose trail is returned, adding no format or identifier details, so the schema largely does the work.

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?

Names a specific resource (hash-chained audit events) scoped to an envelope and states the ordering, so an agent knows exactly what comes back. It doesn't explicitly contrast with siblings like verify_envelope or get_envelope, but the resource distinction is sharp enough to route correctly.

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 when-to-use or when-not-to-use guidance, no mention of alternatives, and no stated prerequisites. The intent (fetch an envelope's audit log) is only implied by the tool name and the phrase 'for an envelope'.

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