Fiji MCP Server

by surajinacademia

Overview Schema Source Related Servers Discussions Admin

Python

Local

clear_session_trace

Read-onlyIdempotent

Clears the in-process session trace in Fiji without closing images. Use to reset trace history during a session.

Instructions

Clear the in-process session trace (does not close Fiji images).

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`ok`	No
`cleared`	Yes	Number of trace rows removed.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.3May 27, 2026

TDQS

A3.6/5.0

Behavior1/5

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

The description states 'clear' which is a mutating action, but annotations declare readOnlyHint=true and idempotentHint=true, creating a contradiction. The description does not resolve this inconsistency; it fails to accurately reflect the behavioral safety profile intended by the annotations.

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 a single sentence that immediately states the action and adds a clarifying negation. It is concise, front-loaded, and contains no superfluous information.

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 no parameters and presence of output schema and annotations, the description adequately covers the tool's core function and adds context about not closing images. However, the contradiction with annotations reduces completeness.

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?

There are no parameters, so the description does not need to add parameter semantics. Schema coverage is 100%, and the description is sufficiently clear for a parameterless tool.

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 clears the in-process session trace and explicitly clarifies it does not close images, distinguishing it from potential confusion with image operations. The purpose is specific and unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

While the description implies usage for clearing traces, it provides no explicit guidance on when to use this tool versus alternatives (e.g., get_session_trace) or any prerequisites. The lack of parameters simplifies usage, but guidelines are absent.

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