Skip to main content
Glama

Update Chatmode from Source

update_chatmode_from_source

Update a .chatmode.md file from its source definition to maintain synchronization between chat modes and their source files.

Instructions

Update a .chatmode.md file from its source definition.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filenameYesThe filename of the chatmode to update from source (with or without extension)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The core handler function for the 'update_chatmode_from_source' tool, which currently returns a placeholder 'Not implemented' message as the feature is not yet implemented.
    def update_chatmode_from_source(
        filename: Annotated[str, "The filename of the chatmode to update from source (with or without extension)"],
    ) -> str:
        """Update a .chatmode.md file from its source definition."""
        return "Not implemented"
  • Registers the 'update_chatmode_from_source' tool with the FastMCP app inside the register_chatmode_tools function, specifying name, description, tags, annotations, and metadata.
    @app.tool(
        name="update_chatmode_from_source",
        description="Update a .chatmode.md file from its source definition.",
        tags={"public", "chatmode"},
        annotations={
            "idempotentHint": False,
            "readOnlyHint": False,
            "title": "Update Chatmode from Source",
            "parameters": {"filename": "The filename of the chatmode to update from its source. If .chatmode.md extension is not provided, it will be added automatically."},
            "returns": "Returns a success message if the chatmode was updated from source, or an error message. Note: This feature is currently not implemented.",
        },
        meta={
            "category": "chatmode",
        },
    )
  • Schema definition via annotations, including input parameters (filename), return description, and hints for idempotency and read-only status.
    annotations={
        "idempotentHint": False,
        "readOnlyHint": False,
        "title": "Update Chatmode from Source",
        "parameters": {"filename": "The filename of the chatmode to update from its source. If .chatmode.md extension is not provided, it will be added automatically."},
        "returns": "Returns a success message if the chatmode was updated from source, or an error message. Note: This feature is currently not implemented.",
    },
Behavior3/5

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

Annotations already indicate this is a write operation (readOnlyHint: false) and not idempotent (idempotentHint: false). The description adds minimal behavioral context by specifying it updates 'from its source definition,' suggesting it might regenerate content from an external source. However, it doesn't elaborate on what 'source definition' means, potential side effects, or error conditions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's function without unnecessary words. It's appropriately sized for a tool with one parameter and good schema coverage, making it easy for an agent to parse quickly.

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?

Given the presence of both annotations and an output schema, the description doesn't need to cover behavioral safety or return values. However, for a mutation tool that updates files, the description could better explain what 'source definition' entails and how this differs from sibling tools like 'update_chatmode' to provide more complete operational context.

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?

With 100% schema description coverage, the input schema fully documents the single 'filename' parameter. The description adds no additional parameter semantics beyond what's already in the schema, so it meets the baseline expectation without providing extra value about parameter usage or constraints.

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 clearly states the action ('Update') and target resource ('.chatmode.md file'), making the purpose understandable. However, it doesn't differentiate from sibling 'update_chatmode' which appears to be a similar operation, leaving some ambiguity about when to use this specific tool versus that alternative.

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?

The description provides no guidance on when to use this tool versus alternatives like 'update_chatmode' or 'create_chatmode'. It doesn't mention prerequisites, constraints, or typical scenarios for updating from source versus other update methods, leaving the agent with insufficient context for proper tool selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/NiclasOlofsson/mode-manager-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server