Skip to main content
Glama
Sign In
ASCII Motion MCP

ASCII Motion MCP

by CameronFoxly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_frame_name

Assign or update a frame's name by specifying its index and new name. Useful for organizing frames in ASCII animations.

Instructions

Set or change the name of a frame

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": {
      "index": "<index>",
      "name": "<name>"
    },
    "name": "set_frame_name"
  }
}

Input Schema

NameRequiredDescriptionDefault
indexYesFrame index
nameYesNew frame name

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 provided, so the description must disclose behaviors. It only says 'set or change the name' with no mention of side effects, error handling, or requirements (e.g., whether the frame must exist). The description is minimal and fails to reveal potential 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, front-loaded with the verb, and contains no unnecessary words. It efficiently conveys the tool's purpose.

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 setter tool with no output schema, the description is fairly complete. However, it does not mention error conditions (e.g., invalid index) or confirm success behavior, but given the tool's simplicity, it is mostly adequate.

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?

Input schema has 100% description coverage, so baseline is 3. The description adds no additional meaning beyond what the schema already provides (frame index and new name).

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 action ('set or change') and the resource ('name of a frame'). It distinguishes the tool from siblings like add_frame or delete_frame, which have different purposes.

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 on when to use this tool vs alternatives. The description lacks context about prerequisites (e.g., if the frame must exist) or scenarios where another tool might be more appropriate.

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