compose-bridge

by TechsOneAi

Overview Schema Source Related Servers Discussions Admin

Python

Local

This server has been deprecated

Rebranded to ComposeLint AI. Repository has been moved to TechsOneAi/ComposeLintAI.

get_token_siblings

Read-onlyIdempotent

Finds semantically related token variants, such as PrimaryDark and PrimaryLight, by naming pattern and semantic link. Use it to explore related tokens or check existing color variants.

Instructions

Read-only. Returns semantically related tokens (e.g., Primary → PrimaryDark, PrimaryLight).

What it does: Finds related variants of a token based on naming patterns and semantic links.
When to use: When exploring related tokens or checking which color variants already exist.
When NOT to use: Does NOT include the original token. Returns empty list if no siblings.
Side effects: Read-only. No files modified.
Parameters:
  - token_name: exact token name (e.g., 'Primary') or fully-qualified (e.g., 'AppColors.Primary').
Returns:
  JSON string with list of sibling token names and current values.

Input Schema

Name	Required	Description	Default
`token_name`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026
RemovedOct 22, 2026
First observedv0.1.0Oct 19, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, making the repeated 'Read-only' and 'No files modified' statements redundant. The description still adds useful behavioral context by specifying that the original token is excluded and that an empty list is returned when no siblings exist.

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 sectioned, front-loaded, and easy to scan, with only minor redundancy such as repeating read-only behavior twice and including a return-value summary despite an output schema. Most sentences earn their place.

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

Completeness5/5

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

Given a single-parameter read-only tool with rich annotations and an output schema, the description covers purpose, usage conditions, exclusions, parameter format, and return behavior. An agent has everything needed to call it correctly.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must carry parameter meaning. It does this well by explaining that token_name accepts either an exact name like 'Primary' or a fully-qualified name like 'AppColors.Primary', adding format detail beyond the bare string schema.

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 states a specific verb and resource ('Returns semantically related tokens') with a concrete example (Primary → PrimaryDark, PrimaryLight) and distinguishes the result from the original token. An agent can understand the tool's unique function without opening the schema.

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

Usage Guidelines4/5

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

It gives explicit when-to-use ('exploring related tokens or checking which color variants already exist') and when-not-to-use guidance (no original token, empty list if none exist). It does not name sibling alternatives such as list_tokens or find_token_by_color, so it falls just short of full routing guidance.

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