Skip to main content
Glama
Sign In
ASCII Motion MCP

ASCII Motion MCP

by CameronFoxly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_cells_batch

Set multiple cells in a single operation to update ASCII art efficiently, reducing API calls.

Instructions

Set multiple cells in a single operation. More efficient than calling set_cell repeatedly.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cells": "<cells>"
    },
    "name": "set_cells_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
cellsYesArray of cells to set (max 10,000). Each cell can specify any combination of char, color, bgColor.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.4

TDQS

A3.7/5.0
Behavior2/5

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

Without annotations, the description must disclose behavioral traits. It fails to mention important details such as whether it overwrites existing cells, error handling behavior, or authorization requirements. The 10,000 cell limit is only in the schema, not highlighted in the description.

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 two sentences long, direct and informative without extra fluff. Every sentence adds value, front-loading the core purpose and efficiency benefit.

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 complexity of a batch operation with optional fields and no output schema or annotations, the description is minimally adequate. It covers the basic use case but lacks details on return values, partial failures, or transactional guarantees.

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%, providing detailed parameter descriptions including max 10,000 items. The description adds no extra semantic meaning beyond the schema, meeting the baseline but not exceeding it.

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 sets multiple cells in a single operation, using specific verb 'set' and resource 'multiple cells'. It distinguishes itself from the sibling tool 'set_cell' by highlighting efficiency, making its purpose immediately clear.

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 usage for batch cell updates and notes efficiency over repeated 'set_cell' calls. However, it lacks explicit guidance on when not to use it (e.g., for single cell operations) or other alternatives, which would be helpful.

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