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.

list_modified_files

Read-onlyIdempotent

Lists files changed by recent replace_pattern operations in the current session so you can review unapproved modifications before approving or rejecting them.

Instructions

Read-only. Lists files modified by recent replace_pattern operations in the current session.

What it does: Queries the session journal to return all files currently in a modified state.
When to use: To see what files have unapproved changes before approving or rejecting.
When NOT to use: Does NOT persist across sessions. For git-based modifications use get_file_diff. Returns files in journal (not git status).
Side effects: Read-only. No files modified.
Parameters: None.
Returns:
  JSON string with list of relative file paths.

Input Schema

Name	Required	Description	Default
No arguments

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

Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint, so the safety profile is covered, but the description adds genuinely new behavior: results come from the session journal rather than git status and do not survive session boundaries. Minor credit lost for restating 'Read-only. No files modified.' twice, which duplicates readOnlyHint.

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?

Labeled sections are front-loaded and scannable, with the scoping caveat appearing before the tool is ever called. The only waste is the duplicated read-only statement in the opening line and the 'Side effects' section.

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 no-argument, read-only list tool this covers purpose, usage boundary, session lifetime, source of truth, and return shape. Nothing an agent needs in order to select or call it is missing.

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?

Zero parameters, so the baseline is 4; 'Parameters: None.' is consistent with the empty schema and prevents an agent from looking for filter arguments. Nothing further is needed or possible here.

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 ('Lists files modified by recent replace_pattern operations') plus the scoping qualifier 'in the current session'. That scope detail distinguishes it from the git-oriented sibling get_file_diff without the agent needing to open any 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?

Contains explicit 'When to use' (reviewing unapproved changes before approve/reject) and 'When NOT to use' (cross-session persistence; git-based diffs → get_file_diff). It names the alternative and the condition that selects it, which is exactly what routing requires among 30+ siblings.

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