Skip to main content
Glama
Sign In
ASCII Motion MCP

ASCII Motion MCP

by CameronFoxly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

export_react

Export ASCII animation as a reusable React component, with option for TypeScript and play/pause controls.

Instructions

Export the animation as a React component (JSX or TSX).

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

Input Schema

NameRequiredDescriptionDefault
filePathNoFile path to save to
typescriptNoUse TypeScript (TSX)
includeControlsNoInclude play/pause controls
componentNameNoReact component nameAsciiAnimation

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?

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states what the tool does, without revealing side effects (e.g., file writes), execution context, or whether it modifies the animation state. The description lacks details on behavioral traits.

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 description is a single, front-loaded sentence that conveys the core purpose efficiently. Every word is useful, though it could benefit from minor elaboration on the output type. It remains concise without unnecessary verbosity.

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

Completeness2/5

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

Despite high schema coverage, the description lacks overview context. It does not mention that the tool saves to a file (filePath parameter) or any output format details. For a tool with 4 parameters and no output schema, the description should provide more context about the export process and result.

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% with each parameter having a description. The tool description does not add extra meaning beyond the schema; it simply repeats the export purpose. Baseline 3 is appropriate as the schema already documents all parameters adequately.

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 exports an animation as a React component, specifying JSX or TSX. It uses a specific verb ('Export') and resource ('animation as a React component'), effectively distinguishing it from sibling export tools like export_html or export_json.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., export_html, export_bubbletea). It does not mention prerequisites, when not to use it, or suggest sibling tools for different export formats.

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