Skip to main content
Glama
Sign In
ASCII Motion MCP

ASCII Motion MCP

by CameronFoxly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

suggest_palette_for_style

Recommends a color palette that matches a chosen ASCII art style, such as terminal or retro. Use it to quickly select appropriate colors for your ASCII creations.

Instructions

Get palette recommendations for a specific style.

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": {
      "style": "<style>"
    },
    "name": "suggest_palette_for_style"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleYesStyle theme

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.4

TDQS

C2.9/5.0
Behavior2/5

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

Without annotations, the description carries the burden of explaining behavior. It only says 'get recommendations', but does not clarify if this is a read-only operation, what the output format is, or how recommendations are generated. This is insufficient for a tool with no annotations.

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 sentence with no redundant information. It is front-loaded and concise. However, it might be slightly too brief, missing details that could improve clarity.

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?

Given the complexity of palette-related sibling tools and the lack of output schema, the description should explain what 'recommendations' entails (e.g., returns a single palette or multiple, how they are selected). This omission leaves the agent underinformed.

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?

The sole parameter 'style' is fully described with an enum in the schema (100% coverage). The description adds no extra meaning beyond 'Style theme'. With high schema coverage, baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states 'Get palette recommendations for a specific style', indicating a specific action (get recommendations) and resource (palette) linked to a style parameter. However, it does not differentiate from sibling tools like 'list_color_palettes' or 'get_color_palette', which could cause confusion.

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 versus alternatives such as 'list_color_palettes' or 'get_color_palette'. The description lacks context about preferred scenarios or when not to use it.

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