Climate MCP Server

get_audit_trail

Retrieve a compact audit trail showing which tools, datasets, and columns have been used so far in the current run. Call anytime mid-run for inspection.

Instructions

    Returns the compact audit trail for the current run:
    which tools were called, which dataset and columns each used.
    Call at any point mid-run to inspect what has been executed so far.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 30, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. It discloses the tool returns a compact audit trail, but does not elaborate on side effects (e.g., read-only nature), performance implications, or format. 'Compact' hints at limited data, but more detail would improve transparency.

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 sentences with no wasted words. Front-loaded with main purpose and a clear usage instruction. Every sentence earns its place.

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?

Given zero parameters and an output schema present, the description adequately explains what the tool does and when to use it. It could mention that it only shows the current run, but that is implied. Sufficient for a simple inspection tool.

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 has zero parameters and schema coverage is 100% (vacuous). Per guidelines, baseline is 4 for 0 parameters. Description adds no parameter info, but none is needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the tool returns the compact audit trail for the current run, listing tools called and dataset/columns used. It is a specific verb+resource and distinguishes from sibling tools which focus on summaries, fund details, or reporting.

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?

Explicitly states 'Call at any point mid-run to inspect what has been executed so far', providing clear when-to-use guidance. No explicit alternatives or when-not-to-use, but context implies it is for runtime inspection, and siblings cover different use cases.

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