Skip to main content
Glama

Theme DIYA

get_theme
Read-onlyIdempotent

Turns a brand color (and, if wanted, glass, a font and corners) into the one DiyaProvider line to write. Shows the accent tokens DIYA derives with their contrast, and says when a color will look faint.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_theme"
  }
}

Input Schema

NameRequiredDescriptionDefault
glassNo
themeNo
motionNo"reduced" for fades only, "off" for none; "system" (the default) follows the device's Reduce Motion setting
cornersNoCorner scale: 0 square, 1 default, 2 round
brandColorNoA hex color, such as "#1F4E7A", or { light, dark }
fontFamilyNoA CSS font-family stack

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value beyond that: it says the return is a single DiyaProvider line plus the derived accent tokens with their contrast ratios, and that faint colors are flagged — output semantics that no annotation or output schema supplies. It loses a point only because it does not say what form the contrast/warning information takes.

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?

Two sentences, front-loaded on the core transformation, with no filler or repetition of the name. The parenthetical '(and, if wanted, glass, a font and corners)' is slightly compressed and verbless, which costs a little clarity, but nothing is wasted.

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?

With six parameters, no output schema and a purely read-only profile, the description does the important extra work of characterizing the return value and its color-contrast warnings. What remains thin is the effect of theme and motion on the emitted provider line, which an agent would have to infer from the schema.

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 67%, so the schema already carries much of the meaning, and the description adds little beyond naming four of the six inputs (brand color, glass, font, corners). It says nothing about theme or motion, and theme's enum has no schema description at all, leaving one parameter undocumented in both places. That is roughly baseline for a partially covered schema.

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?

The description states a concrete transformation: a brand color (plus optional glass, font, corners) becomes 'the one DiyaProvider line to write', and it names the derived output (accent tokens with contrast). That is a specific verb-plus-resource statement. It stops short of a 5 because it never distinguishes itself from the sibling list_tokens, which by name plausibly also surfaces tokens, so an agent could hesitate between the two.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'if wanted' signals that glass, font and corners are optional, and 'the one DiyaProvider line to write' implies the setup-time use case. But there is no explicit when-to-use or when-not-to-use guidance, no mention of prerequisites, and no routing away from list_tokens or get_setup. Usage is only implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources