Skip to main content
Glama

request_install

Submit an add-on installation request for user approval in the dashboard, showing what would be installed, source, disk cost and licence status. Nothing is downloaded until the user approves.

Instructions

Ask the user to approve installing an add-on. Nothing is downloaded by this call.

The request appears in the dashboard with what would be installed, from where, the disk cost and the licence situation. Only the user can approve or reject it there. reason: one sentence for the user on why you need it.

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": {
      "backend": "<backend>"
    },
    "name": "request_install"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNo
backendYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that nothing is downloaded, that the request is surfaced in a dashboard with install source, disk cost and licence details, and that only the user can approve or reject. The one gap is that it never says what the call returns or how to later check the outcome (the install_status sibling is never referenced).

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?

Three short sentences plus a parameter hint, with the most important constraint ('Nothing is downloaded by this call') front-loaded in sentence one. The trailing 'reason:' line is slightly awkwardly formatted but earns its place by defining the expected content.

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?

For a two-parameter tool with no output schema and no annotations, the description covers the human-in-the-loop flow, what the user will see, and the non-destructive nature of the call. It falls short only on the meaning of the required 'backend' argument and on how to observe the request's resolution afterward.

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% for both parameters. The description explains 'reason' well ('one sentence for the user on why you need it'), but 'backend' — the only required parameter — is never explained, so the agent gets no guidance on what identifier form to supply.

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?

The first sentence names a specific verb and resource ('Ask the user to approve installing an add-on') and immediately scopes it against the obvious confusion ('Nothing is downloaded by this call'), which separates it from a real install action and from the request_uninstall sibling.

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 rather than stated: the agent learns the request goes to the dashboard and that only the user can approve or reject, which implies this is the correct tool when a human decision is required. There is no explicit when-to-use/when-not statement and no routing to install_status for follow-up, so the agent must infer the workflow.

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