Skip to main content
Glama

generate_client_config

Generates or writes ready-to-paste MCP client configuration snippets for Claude Desktop, Cursor, Gemini, and VS Code Cline.

Instructions

Generates or writes ready-to-paste MCP client configuration snippets for Claude Desktop, Cursor, Gemini, and VS Code Cline.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "client": "<client>"
    },
    "name": "generate_client_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
writeNoAutomatically write or merge into the client configuration file on disk.
clientYesTarget AI client application.
outputPathNoCustom file path to write the configuration to.
serverNameNoMCP server key name (default: "evidence").evidence
workspacePathNoOptional workspace path to bind the server to.
useGlobalBinaryNoUse global "evidence-mcp" binary instead of node dist/cli.js.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It hints at a dual mode (generate versus write) but never discloses that write mode mutates files on disk, whether it merges or overwrites, where files land by default, or what can be destroyed - all essential for a tool with disk side effects.

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?

A single tight sentence with the resource front-loaded and the supported clients enumerated at the end. No filler, no redundancy.

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?

With no annotations and no output schema, the description should say more about what the generated snippet contains and how write mode behaves. The rich 100%-covered input schema compensates for parameter gaps, but the side-effecting behavior of the write path is left unexplained.

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?

Schema description coverage is 100%, so all six parameters (including the write flag, outputPath, serverName, and useGlobalBinary) are already documented in the schema. The description only echoes the client list, adding no meaning about parameter interactions such as write combined with outputPath.

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 names a specific verb (generates or writes) and resource (MCP client configuration snippets) and enumerates the four target clients, which matches the client enum. It doesn't explicitly position itself against the evidence-oriented siblings, but the config-generation purpose is unmistakably distinct from all of them.

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?

Usage is implied by the purpose: call it when you need a client config snippet for one of the four listed clients. There is no explicit when-to-use framing, no prerequisites, and no guidance on choosing generate-only versus write mode, so the agent must infer the decision from the schema.

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