Skip to main content
Glama

crafty_update_config

Modify Crafty Controller panel settings to adjust server management parameters and customize operational behavior.

Instructions

Update Crafty Controller panel configuration settings

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
configYesConfiguration key-value pairs to update

Implementation Reference

  • The handler function for 'crafty_update_config', which updates the Crafty Controller panel configuration.
    server.tool(
      "crafty_update_config",
      "Update Crafty Controller panel configuration settings",
      {
        config: z.record(z.string(), z.unknown()).describe("Configuration key-value pairs to update"),
      },
      async ({ config }) => {
        try {
          const data = await client.patch("/crafty/config", config);
          return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
        } catch (error) {
          const msg = error instanceof Error ? error.message : String(error);
          return { content: [{ type: "text", text: `Error: ${msg}` }], isError: true };
        }
      }
    );
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Update' implies a mutation operation, it doesn't specify whether this requires authentication, what permissions are needed, whether changes are reversible, or potential side effects. This leaves significant behavioral gaps for a configuration update tool.

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 with zero wasted words. It's appropriately sized for a simple update operation and front-loads the essential information without unnecessary elaboration.

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

Completeness2/5

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

For a configuration update tool with no annotations and no output schema, the description is insufficient. It doesn't explain what configuration settings are available, what format the key-value pairs should use, what happens on success/failure, or return values. The agent lacks critical context for proper tool invocation.

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?

The schema description coverage is 100%, with the single parameter 'config' well-documented as 'Configuration key-value pairs to update.' The description doesn't add any meaningful parameter semantics beyond what the schema already provides, which is acceptable given the high schema coverage.

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 ('Crafty Controller panel configuration settings'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from its sibling 'crafty_get_config' or other configuration-related tools, which prevents a perfect score.

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 'crafty_get_config' for reading configuration or other update tools. There's no mention of prerequisites, context, or exclusions, leaving the agent with minimal usage direction.

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/HadiCherkaoui/crafty-mcp'

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