Skip to main content
Glama

Get install config

get_install_config
Read-onlyIdempotent

Ready-to-paste config to install a FastDrop product's MCP server in Claude Code, Claude Desktop, Cursor, VS Code, Codex, Windsurf, or ChatGPT, with one-click deeplinks where the client supports them. Use when the user asks how to install, connect, or add a server found on FastDrop. Secrets are always values.

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

Input Schema

NameRequiredDescriptionDefault
slugYesProduct slug
clientNoOnly return config for this client. Default: all clients.

Output Schema

NameRequiredDescriptionDefault
nameNo
pageNo
slugYes
configsYes
verifiedNo
warningsYes
transportYes
authRequiredNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety bar is lower. The description adds non-obvious behavior the annotations cannot convey: one-click deeplinks are provided only where the client supports them, and secrets are always placeholder values rather than real credentials. It does not say what happens for unsupported clients or invalid slugs.

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?

Two sentences, deliverable described first, usage trigger second, with the secret-placeholder caveat appended compactly. No redundant restatement of the title or name.

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?

An output schema exists, so return-value explanation is not required, and the description still characterizes the payload (per-client config, deeplinks). It covers secret handling, which is the main behavioral surprise. Minor gap: no statement about error or fallback behavior when a client is unsupported.

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 coverage is 100% and the enum of clients is fully documented in the schema, so the description need not re-explain parameters. It adds no semantics for 'slug' or 'client' beyond what the schema states, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific deliverable ('Ready-to-paste config to install a FastDrop product's MCP server') and enumerates the supported clients, so the agent knows exactly what comes back. No sibling tool produces install configuration, and the description makes that distinct scope obvious.

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

Usage Guidelines4/5

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

Gives an explicit trigger: 'Use when the user asks how to install, connect, or add a server found on FastDrop.' That is clear context for invocation, though it does not state when not to use it or what to do if the product has no MCP server.

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.

Resources