HostedMCP Directory

Get install config

get_install_config

Read-onlyIdempotent

The exact config snippet (or CLI command) to add an MCP server to a client, with the file it goes in and the client's setup steps.

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

Input Schema

Name	Required	Description	Default
`name`	Yes
`owner`	Yes
`client`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already establish readOnly, idempotent, closed-world, and non-destructive behavior, so the bar is low. The description goes beyond them by disclosing the return payload (config snippet or CLI command, the file it belongs in, and setup steps), which matters since there is no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, front-loaded sentence with no filler; the most useful clause (exact config snippet) comes first. It is a noun phrase rather than a full sentence, which is terse but still readable.

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?

For a simple three-parameter read tool with no output schema, the description adequately says what comes back. It falls short on how owner and name combine to identify a server and on what happens with an unsupported client value.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning, but it only vaguely gestures at 'an MCP server' and 'a client'. It never explains the owner parameter (presumably the publisher/namespace) or that client is restricted to a fixed enum of supported clients, leaving two of three parameters unexplained.

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 artifact (the exact config snippet or CLI command plus target file and setup steps) for adding an MCP server to a client, which is far more specific than a restatement of the name. It does not explicitly contrast with get_server, but the resource is unambiguous.

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 only implied: an agent can infer it should call this when it needs installation instructions for a specific server/client pair. There is no explicit when-to-use versus get_server, and no statement that the client must be one of the supported integrations.

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

All HostedMCP Directory tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?