set_foreground_color
Set the foreground text color in ASCII art using a hex color code.
Instructions
Set the active foreground (text) color.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| color | Yes | Hex color (e.g., #FF0000) |
Set the foreground text color in ASCII art using a hex color code.
Set the active foreground (text) color.
| Name | Required | Description | Default |
|---|---|---|---|
| color | Yes | Hex color (e.g., #FF0000) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, and description does not disclose behavioral traits (e.g., mutation effects, scope, or persistence). Merely stating 'Set' is insufficient without annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, fully front-loaded, no unnecessary words. Every part earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool is simple (1 param, no output schema), but description lacks context about side effects or prerequisites. Adequate for basic use but could mention it sets color for subsequent text operations.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema covers 100% of parameters with pattern and description for 'color'. Description adds no extra meaning beyond schema, so baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states verb 'Set' and resource 'active foreground (text) color', distinguishing it from siblings like 'set_background_color' and other setter tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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. Missing context about prerequisites or conditions, such as whether it interacts with selection or layers.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/CameronFoxly/ascii-motion-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server