Skip to main content
Glama
TrialRun MCP

TrialRun MCP

by kostadindev

Audit log

get_audit_log

Retrieve timestamped gateway events, restricted-data leak summaries, and a preliminary Data Stewardship score to review what agent file access reached the model, using labels and redacted snippets.

Instructions

Timestamped gateway events, restricted-data leak summary and a preliminary Data Stewardship score (Full / Partial / Zero). Contains labels and redacted snippets only.

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_log"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose real behavioral traits: output is labels and redacted snippets only, it includes a leak summary, and the stewardship score is only preliminary. It does not state read-only semantics (implied only by the 'get_' prefix), time window, result size, or whether the score is cached/stale, which are the facts an agent most needs before trusting the output.

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 dense sentence with no filler, front-loading the main payload and appending the redaction caveat last. Every clause adds information an agent would otherwise lack.

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?

There is no output schema and no annotations, so the description must explain the return value, and it partially does by enumerating the three components and score levels. It leaves out result scope, volume, and freshness, which matter for a no-argument read tool whose output drives a stewardship judgment.

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?

The tool takes zero parameters, so there is no parameter meaning to convey; the schema is empty and 100% covered. Baseline for a parameterless tool is 4, and nothing in the description misrepresents the calling contract.

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 concrete payload: timestamped gateway events, a restricted-data leak summary, and a Data Stewardship score with enumerated values (Full / Partial / Zero). That is far more specific than the bare name, but it never states the retrieval scope (all history? current session?) or a verb, so an agent still has to infer what set of records it gets back.

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?

No when-to-use guidance and no named alternative among the siblings (get_report, get_access_policy, check_text). The phrase 'preliminary Data Stewardship score' weakly implies triage/assessment use, but nothing tells the agent when to prefer this over get_report or when not to call it.

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