FigTreeKit-MCP

setup_figtree

Prepare FigTree for rendering by downloading and compiling the patched JAR, using an existing whitelisted JAR, or checking dependencies only.

Instructions

Download (or use given jar) and compile the patched FigTree JAR.

Args: jar_path: Optional existing JAR to use (whitelisted; no compile). check_only: Only check dependencies (no download/compile). verbose: Print step-by-step setup progress.

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

Input Schema

Name	Required	Description	Default
`verbose`	No
`jar_path`	No
`check_only`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 20, 2026

TDQS

A3.5/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 behavioral burden. It does disclose meaningful traits: a network download, a compile step, that jar_path is whitelisted and suppresses compilation, and that check_only suppresses both steps. It omits where artifacts are written, failure modes, and permission/network requirements, so it is adequate rather than rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence front-loads the core action, and the Args list is compact and scannable with zero filler. No wasted sentences, though the arg lines are terse enough to feel like schema restatement in places.

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?

An output schema exists, so return values need not be explained. For a tool that downloads and compiles, though, the description says nothing about dependencies required, environment assumptions, or what happens on a failed compile, leaving gaps an agent would need to discover by calling.

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?

Schema description coverage is 0%, so the description must compensate, and it largely does: all three parameters are given semantics beyond their types (jar_path whitelisted and no-compile, check_only skips download/compile, verbose prints progress). It stops short of format examples or default-value restatement.

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?

States a specific verb and resource: downloads or uses a provided JAR and compiles the patched FigTree JAR. An agent can distinguish it from siblings like check_figtree or get_environment, though the description never names or contrasts those alternatives explicitly.

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?

The Args block implies usage conditions (pass jar_path to skip compilation, set check_only to only verify dependencies), which is genuine conditional guidance. However, it never says when to prefer this tool over check_figtree or get_environment, nor what prerequisites (Java, network) are required.

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