SpriteMCP

Overview Schema Source Related Servers Discussions Admin

get_output_root

Get the absolute output root currently in effect for sprite generation, whether session-specific or default. Use this to determine the save location for your painted pixel characters and animations.

Instructions

Return the absolute output root currently in effect (session or default).

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 25, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden and does well by specifying that the tool returns the current effective value and that this value may come from a session override or the default. 'Return' also strongly implies a non-mutating operation, which is appropriate for the tool.

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, front-loaded sentence with no filler. Every phrase adds value: 'absolute', 'currently in effect', and '(session or default)' all clarify the exact behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a parameterless getter with an output schema, the description is complete. It identifies what is returned, the scope of that value, and the read-only nature of the operation, leaving no ambiguity for an agent to select or invoke it.

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 and the schema already reflects that with 100% coverage. The baseline of 4 applies because there are no parameters for the description to clarify.

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 uses the specific verb 'Return' with a clearly defined resource: the absolute output root currently in effect, including the session-or-default distinction. This clearly identifies it as the getter counterpart to the sibling tools set_output_root and clear_output_root.

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 makes clear this is the tool to call when you need the current effective output root, and its 'Return' semantics distinguish it from mutation siblings like set_output_root and clear_output_root. It does not explicitly name alternatives, but the context is unambiguous for a no-parameter getter.

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