Skip to main content
Glama

List DIYA tokens

list_tokens
Read-onlyIdempotent

The public --diya-* CSS custom properties with their Light and Dark values, which provider prop sets each, and which to change together.

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": "list_tokens"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupNosurfaces, text, actions, statuses, space, shape, type-scale, glass, …

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, closed-world, non-destructive), so the lower bar applies. The description still adds value by disclosing the shape of the payload — paired Light/Dark values, provider prop set attribution, and co-change grouping — which the agent would otherwise not know since there is no output schema.

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?

A single dense sentence with no filler, and the most identifying detail (--diya-* custom properties) is front-loaded. It borders on being a fragment list rather than a sentence, but every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-optional-parameter read tool this is close to sufficient, and the missing output schema is partly compensated by the description enumerating the returned fields. However, it never explains the 'group' parameter's effect (filtering vs. grouping) or the overall response structure, leaving a real gap.

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 description coverage is 100% and the single optional 'group' parameter is documented in the schema with a rich list of example values (surfaces, text, actions, statuses, space, shape, type-scale, glass). The description never mentions grouping or filtering at all, so it adds nothing beyond the schema; baseline 3 applies.

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 names a specific resource (public --diya-* CSS custom properties) and enumerates the returned facets: Light/Dark values, provider prop set membership, and change-together grouping. It is clearly distinguishable from get_component, get_setup, get_theme, and search_components, though the action verb ('list/return') is only implied by the name and title rather than stated.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no routing to the closest sibling, get_theme, which plausibly overlaps for theming data. An agent must infer that this is the tool for inspecting individual CSS variables rather than whole themes.

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