Skip to main content
Glama
Sign In
ASCII Motion MCP

ASCII Motion MCP

by CameronFoxly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

new_project

Start a new ASCII art project with a blank canvas. Choose from preset templates or set custom dimensions.

Instructions

Create a new empty project, discarding any unsaved changes

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

Input Schema

NameRequiredDescriptionDefault
widthNoCanvas width
heightNoCanvas height
nameNoProject name
templateNoUse a preset template

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.4

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It explicitly states that unsaved changes are discarded, which is a critical behavioral trait. However, it does not mention other behaviors such as whether confirmation is required or what the output/next state is.

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, front-loaded with the core purpose and key side effect. Every word is necessary and there is no redundancy.

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?

For a simple creation tool with four parameters and no output schema, the description covers the main action and side effect. It could mention the default behavior for parameters or the empty project state, but overall it is sufficient.

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 the description does not need to add param details. It adds no extra meaning beyond what the schema already provides (width, height, name, template with descriptions). Baseline score is appropriate.

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 'Create a new empty project', specifying the verb and resource. It also adds 'discarding any unsaved changes', which differentiates it from saving or loading actions and highlights a key aspect.

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 implies when to use (starting fresh) by mentioning discarding unsaved changes, but it does not explicitly list alternatives or conditions like 'save before creating if needed'. The context is clear enough though.

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