Skip to main content
Glama
Sign In
ASCII Motion MCP

ASCII Motion MCP

by CameronFoxly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

export_ansi

Export a frame as ANSI-encoded text for terminal display. Choose color mode (16, 256, or truecolor) to match terminal capabilities.

Instructions

Export the current frame with ANSI escape codes for terminal display.

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

Input Schema

NameRequiredDescriptionDefault
frameIndexNoFrame to export (defaults to current)
colorModeNoANSI color modetruecolor

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.4

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description bears full responsibility for behavioral disclosure. It indicates a read operation (export) but omits details such as output format, side effects (e.g., file creation), or required permissions. The phrase 'for terminal display' is vague about how the data is returned.

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 of 11 words, directly stating the tool's purpose with no redundant or extraneous information. It is optimally concise for a simple export operation.

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?

Given the absence of an output schema and annotations, the description should ideally explain what the export produces (e.g., a string, a file path) and how it is returned. It only states the purpose, leaving the agent to infer behavior from context. Adequate for simple params but lacks output details.

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 100%, so baseline is 3. The description does not add meaning beyond the schema: both parameters (frameIndex and colorMode) are already described with defaults and meanings. No additional constraints or context are provided.

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?

Description clearly specifies the action ('Export') and resource ('current frame') with format ('ANSI escape codes') and context ('terminal display'). However, it does not differentiate from sibling export tools like export_text or export_html, which could lead to confusion when multiple export options exist.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. Given the large number of sibling export tools, the agent would benefit from explicit conditions or preferences for ANSI export, but none are stated.

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

Deploy Server

Other Tools