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.

suggest_token_split

Read-onlyIdempotent

Analyzes tokens used in multiple contexts and proposes contextual split suggestions before pattern replacement, without modifying files.

Instructions

Read-only analysis. Suggests splitting tokens used in multiple contexts.

What it does: Detects if a token is used in different contexts (e.g. cards and buttons) and proposes contextual splits.
When to use: Use BEFORE replace_pattern.
When NOT to use: For token impact analysis use get_token_impact. For sibling tokens use get_token_siblings.
Side effects: Read-only. No files modified.
Parameters:
  - token_name: optional filter to analyze a specific token only.
  - project_path: optional override for project root path.
Returns:
  JSON string with split suggestions, proposed token names, and affected call sites.

Input Schema

Name	Required	Description	Default
`token_name`	No
`project_path`	No

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.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so 'Read-only. No files modified' largely repeats structured data (twice, in the lead line and the Side effects line). The description does add one piece of behavior beyond annotations: the sequencing constraint that this must run before replace_pattern. No mention of cost, scope limits, or confidence of suggestions.

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?

Well-structured with labeled sections, front-loaded with the key constraint. The 'Read-only' claim appears in both the opening line and the Side effects field, and the Returns section duplicates the output schema, so a little space is wasted.

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?

For a two-optional-parameter read-only analysis tool, the description covers purpose, preconditions, exclusions, parameter meaning, and output shape. Nothing an agent needs in order to call it correctly is missing.

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 0%, so the description must compensate; it does describe both parameters' purpose ('optional filter to analyze a specific token only', 'optional override for project root path'), which is meaningful. However, it adds no format or syntax detail (e.g. expected path shape or token name convention) that the bare schema lacks, so it only partly fills the gap.

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?

States a specific verb and resource ('suggests splitting tokens used in multiple contexts') plus a concrete detection criterion ('cards and buttons'). The explanation of 'what it does' makes it clearly distinguishable from generic token-editing siblings.

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

Usage Guidelines5/5

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

Explicitly says to use it BEFORE replace_pattern, and names two exclusions with the correct alternatives (get_token_impact for impact analysis, get_token_siblings for sibling tokens). An agent needs no inference to route correctly.

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