Skip to main content
Glama

get_config

Retrieve the current merged server configuration to view active context and operational mode settings.

Instructions

Get the current merged server configuration, including active context and mode.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for the 'get_config' tool, which retrieves the server configuration using the provided 'getConfig' function.
    {
      name: "get_config",
      description:
        "Get the current merged server configuration, including active context and mode.",
      schema: {},
      handler: async () => {
        return makeTextResponse(getConfig());
      },
    },
  • Registration of 'get_config' tool inside the GodetteMcpServer class by invoking createConfigTools.
    // Config tools
    for (const tool of createConfigTools(
      () => this.config,
      (mode) => {
        this.switchMode(mode);
      },
    )) {
      this.toolRegistry.register(tool);
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the tool retrieves configuration but doesn't disclose behavioral traits such as permissions needed, whether it's read-only or has side effects, rate limits, or response format. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 front-loads the core purpose ('Get the current merged server configuration') and adds clarifying detail ('including active context and mode'). There is no wasted verbiage, making it highly concise and well-structured.

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 0 parameters and no output schema, the description is minimally adequate. It explains what the tool does but lacks details on return values, error conditions, or behavioral context. For a simple read operation, it meets basic needs but could be more complete by addressing output or usage nuances.

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?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately adds no parameter details, focusing on the tool's purpose. Baseline is 4 for zero parameters, as it avoids redundancy and compensates adequately.

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 ('Get') and resource ('current merged server configuration'), specifying it includes 'active context and mode'. It distinguishes from siblings by focusing on configuration retrieval rather than operations like file management or scene manipulation. However, it doesn't explicitly contrast with similar tools like 'get_project_settings' or 'get_runtime_state'.

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

Usage Guidelines3/5

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

The description implies usage for retrieving configuration details, but provides no explicit guidance on when to use this tool versus alternatives like 'get_project_settings' or 'get_runtime_state'. It lacks prerequisites, exclusions, or comparisons to sibling tools, leaving usage context inferred rather than stated.

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/woohq/godette-mcp'

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