Skip to main content
Glama

set_theme_color

Update a named color slot in the document theme with a hex color. Provide the slot (e.g., dk1, accent1) and a 6-character hex code without #.

Instructions

Update a named color slot in the document theme.

Args: slot: One of dk1, lt1, dk2, lt2, accent1-accent6, hlink, folHlink. hex_color: 6-character hex string without # (e.g. "FF0000").

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slotYes
hex_colorYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

The description only states 'Update' without disclosing behavioral traits such as whether changes are reversible, affect existing elements, or require specific permissions. With no annotations, this is insufficient.

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 concise, uses a clear docstring format, and front-loads the purpose. Every sentence adds value, and there is no extraneous text.

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?

Given the tool's simplicity (2 parameters, straightforward mutation), the description covers parameter constraints well. An output schema exists, so return value explanation is unnecessary. Minor improvement would be noting any validation rules.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% coverage, but the description fully explains the valid values for 'slot' and the format for 'hex_color', adding essential meaning beyond the empty schema properties. It compensates completely.

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 updates a named color slot in the document theme, specifying the resource and action. It distinguishes from other set_* tools by focusing on theme colors, a unique resource among siblings.

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 is provided on when to use this tool versus alternatives. There is no mention of prerequisites, limitations, or when not to use it, leaving the agent to infer context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SecurityRonin/docx-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server