compose-bridge

Overview Schema Source Related Servers Discussions Admin

get_design_file_mappings

Read-onlyIdempotent

Returns current design and registry file mappings from .composebridge/config.json for colors, dimensions, and strings. Use before modifying tokens or to debug token resolution.

Instructions

Returns current design/registry file mappings configured in .composebridge/config.json.

When to use:
- Call before modifying design tokens to inspect which files are mapped for colors, dimensions, and strings.
- Call to verify current target files when debugging token resolution issues.

When NOT to use:
- Do not use to configure or modify file mappings (use set_design_file_mapping instead).
- Do not use to list token names and values (use list_tokens instead).

Side effects:
- None (strictly read-only configuration lookup, does not modify any files).

Args:
    project_root: Optional path to project root.

Input Schema

Name	Required	Description	Default
`project_root`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 1, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the 'Side effects: None (strictly read-only...)' section largely restates structured data. The genuinely additive fact is that mappings come from the .composebridge/config.json file, which is modest added context.

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 front-loaded: one-line purpose followed by clearly labeled when-to-use, when-not-to-use, and side-effect sections. There is mild redundancy in repeating the read-only guarantee and in an Args line that echoes the schema, but no wasted prose.

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?

For a single-optional-parameter read tool with rich annotations and an output schema, the description covers purpose, alternatives, and safety adequately. The only meaningful gap is the fallback behavior when project_root is not supplied.

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

Parameters2/5

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

The single parameter has 0% schema description coverage, so the description must compensate, but it only offers 'project_root: Optional path to project root,' which essentially restates the parameter's title and null default. It does not say what happens when omitted (e.g., whether the current working directory or an auto-detected root is used).

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 ('Returns current design/registry file mappings') plus the source of truth ('.composebridge/config.json'), so an agent can distinguish it from set_design_file_mapping and list_tokens 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 Guidelines5/5

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

Provides explicit 'When to use' conditions (before modifying design tokens, when debugging token resolution) and explicit 'When NOT to use' exclusions that name the correct alternative siblings for each case.

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