Skip to main content
Glama

Get install instructions

get_install_instructions
Read-onlyIdempotent

Exact install steps for one loadout and agent: each file's target path in the project, its raw URL, ready-to-run curl commands, manual steps (e.g. MCP servers for agents without a project config file) and the zip URL.

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": {
      "id": "<id>",
      "agent": "<agent>"
    },
    "name": "get_install_instructions"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesLoadout id, e.g. nextjs-supabase-saas
agentYesCoding agent

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value by explaining output composition, including that manual steps exist for agents without a project config file (e.g. MCP server setup). It still says nothing about caching, failure behavior for unknown loadout/agent combos, or size of the response.

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 dense sentence that front-loads the core purpose and then lists the payload contents, with no filler. It reads as a long run-on list rather than a structured breakdown, which slightly hurts scanability but wastes no words.

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 no output schema, the description correctly takes on the job of describing return values and does so thoroughly. For a 2-parameter read-only lookup with full schema coverage, the main remaining gap is error/failure behavior for invalid id or unsupported agent combinations.

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 both parameters are already documented, including the id pattern example and the agent enum. The description goes beyond the schema by indicating that the agent parameter changes the shape of the result (agents lacking a project config file receive manual steps such as MCP server instructions).

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 concrete verb+resource (install steps for one loadout and agent) and enumerates the returned artifacts: target paths, raw URLs, curl commands, manual steps, zip URL. That enumeration makes it clearly distinct from get_loadout_file (one file) and get_loadout (metadata) without needing to name 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 only implied by the purpose: an agent can infer this is the tool to call when it needs to actually install a loadout. There is no explicit 'use this when / not when' framing and no mention of prerequisites such as needing a valid loadout id from search_loadouts first.

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.