Skip to main content
Glama

Get install config for an AI client

get_install_config
Read-onlyIdempotent

How to add one MCP server or skill to one AI client, taken from the project's own documentation, with where the config goes. Credentials are placeholders, never real values. Clients: claude-code, claude-desktop, cursor, vscode, codex, chatgpt, gemini-cli, windsurf, cline, zed. Show the user the snippet and ask before writing any file.

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": {
      "listing": "<listing>",
      "client": "<client>"
    },
    "name": "get_install_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoNeeded only when a server and a skill share the slug
clientYesAI client slug, e.g. "claude-code", "claude-desktop", "cursor", "vscode", "codex"
listingYesKitbay listing URL or slug

Output Schema

NameRequiredDescriptionDefault
urlNo
fileNo
nameNo
noteNo
typeNo
stepsNo
clientNo
formatNo
reasonNo
snippetNo
sourcesNo
locationNo
availableYes
trescaUrlNo
credentialsNo
engineeringNo
configLocationNo
fromClientSpecificDocsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds real context: output credentials are placeholders and never real values, the snippet is sourced from the project's own documentation, and the agent should confirm with the user before writing any file — all behavior not derivable from annotations.

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?

Three short sentences, front-loaded with the resource and scope, then provenance/safety, then the user-confirmation rule. No filler and nothing repeated from the schema or annotations.

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

Completeness4/5

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

With an output schema present, return-value detail is unnecessary, and annotations cover the safety profile; the description fills the remaining gaps (valid clients, placeholder credentials, confirmation step). The only shortfall is no guidance on failure cases such as an unrecognized client slug or a listing without documented setup.

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?

Schema coverage is 100%, so baseline is 3, but the description enumerates all ten valid client slugs (claude-code, claude-desktop, cursor, vscode, codex, chatgpt, gemini-cli, windsurf, cline, zed), several of which the schema only hints at via examples. It also frames listing as a URL-or-slug choice, adding meaning beyond the raw field.

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 concrete resource (install/config snippet for one MCP server or skill on one AI client) and states provenance ("taken from the project's own documentation") plus scope of what it returns (where the config goes). It is clearly not a listing search or tool-detail lookup like the siblings, though it never explicitly contrasts itself with get_tool or get_listing.

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 singular scope ("one MCP server or skill to one AI client") and reinforced by the operating instruction "Show the user the snippet and ask before writing any file." There is no explicit when-to-use versus get_tool/get_listing guidance and no statement of what to do if the client slug is unsupported.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.