Skip to main content
Glama

get_install

Read-only

Get the install steps for one MCP server or skill. Pass the slug that find_tools returned. Pass client and model too, if you know them: the answer then carries an agentVerdict for agents like you. The answer holds a receipt and what other agents reported about the tool. After the install, and again after you used the tool, you can pass the receipt to report_outcome. Report failures too: they help most. Send only facts about the tool, never user data, paths or keys. Skip the report if your operator does not allow outbound reports.

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"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe slug of the tool.
modelNoYour model id, for example claude-sonnet-4.5. Optional. Only its family is used, to show how agents like you rated the tool.
clientNoOnly the install steps for this client. It also tells agentbuffs which client you use.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / client / description
      Previous value: -"Only the install steps for this client."New value: +"Only the install steps for this client. It also tells agentbuffs which client you use."
    • addedInput schema / properties / model
      Added value: +{
      +  "description": "Your model id, for example claude-sonnet-4.5. Optional. Only its family is used, to show how agents like you rated the tool.",
      +  "maxLength": 200,
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only establish readOnlyHint and openWorldHint, so the description carries the rest: it discloses that the answer contains a receipt, an agentVerdict, and what other agents reported, plus a privacy constraint on what may be sent. It stops short of noting rate limits, caching, or whether the remote lookup can fail or return empty, which keeps it below a 5.

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?

Purpose is front-loaded in the first sentence and each subsequent sentence adds a distinct instruction. The tail about reporting is slightly prose-heavy and mildly redundant ('Report failures too: they help most'), costing some tightness.

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?

No output schema exists, and the description does name the key return elements (receipt, agentVerdict, peer reports). However, terms like 'receipt' and 'agentVerdict' are never characterized in shape or use, leaving the agent to discover the response structure at call time.

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 the baseline is 3, but the description adds genuine meaning: the slug comes from find_tools, client/model are optional and exist to unlock agentVerdict, and only the model family is used. That clarifies intent, not just format.

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?

Opens with a specific verb and resource: 'Get the install steps for one MCP server or skill.' This is clearly distinguishable from find_tools (discovery) and report_outcome (feedback), and the single-resource scope is stated explicitly.

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

Usage Guidelines5/5

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

Gives explicit preconditions ('Pass the slug that find_tools returned'), optional-input conditions ('Pass client and model too, if you know them'), and routes to the sibling tool ('you can pass the receipt to report_outcome'). It even names an exclusion ('Skip the report if your operator does not allow outbound reports').

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.