Skip to main content
Glama
Sign In
ASCII Motion MCP

ASCII Motion MCP

by CameronFoxly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_canvas_preview

Retrieve non-empty cells from a specified region of the ASCII canvas to inspect or preview specific areas.

Instructions

Get non-empty cells in a region. Use for inspecting specific areas.

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

Input Schema

NameRequiredDescriptionDefault
frameIndexNoFrame index (defaults to current)
regionNoRegion to preview (defaults to entire canvas)
maxCellsNoMaximum cells to return

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.4

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states it retrieves data but does not mention read-only nature, auth requirements, rate limits, or side effects. The description is too sparse to inform an agent about safe behavior.

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, efficient sentence that is front-loaded and contains no unnecessary words.

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 having a nested region parameter and no output schema, the description does not explain the return format or clarify that region defaults to entire canvas. It is incomplete for an agent to fully understand usage.

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 clear descriptions for each parameter. The tool description adds nothing beyond the schema, so baseline 3 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 it retrieves non-empty cells in a region, which is a specific verb+resource combination. It distinguishes from siblings like 'get_cell' (single cell) and 'get_canvas_summary' (summary statistics).

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 phrase 'Use for inspecting specific areas' gives a usage context but lacks explicit when-not-to-use or mention of alternatives. It is implied but not explicit.

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