Climate MCP Server

finalize_run

Persists the audit trail by writing the run log to a markdown file and clearing memory. Call at the end of each user query.

Instructions

    Write the full run log to runs/<run_id>.md and clear memory.
    Call once at the end of each user query to persist the audit trail.
    'extra_notes': optional free-text annotation to append to the log.

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": "finalize_run"
  }
}

Input Schema

Name	Required	Description	Default
`query`	No
`extra_notes`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 30, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It reveals the write action and memory clearing, but does not disclose side effects like multiple call behavior or synchronous write. Adequate but could be more explicit.

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?

The description is two sentences, front-loaded with the main action. Every sentence adds value with no redundancy.

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 the tool's simplicity, the description covers purpose and usage timing. It does not detail return values, but an output schema exists. The 'clear memory' phrase could be clarified, but overall sufficient.

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 0%, so the description must compensate. It explains the 'extra_notes' parameter as optional free-text, adding meaning. However, the 'query' parameter is not described, leaving a gap.

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?

The description clearly states the tool writes a full run log to a specific file path and clears memory, using a specific verb and resource. This distinguishes it from siblings like 'start_run' and 'get_audit_trail'.

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?

The description explicitly instructs to call this once at the end of each user query to persist the audit trail, providing clear context. It does not mention exclusions or alternatives, but the sibling set implies this is the finalization step.

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