Skip to main content
Glama

install_status

Check an install or uninstall request, wait for the user's approval decision, and start the work automatically if approved.

Instructions

Check an install or uninstall request. If the user approved it, start the work (when automatic).

wait_seconds: wait up to this long (max 50) for the user's decision.

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": {
      "request_id": "<request_id>"
    },
    "name": "install_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idYes
wait_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two important traits: the call can trigger work as a side effect (a write, not a pure read) and wait_seconds blocks up to 50 seconds. It omits what happens on denial, timeout, or repeated polling, and says nothing about permissions or return values.

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, the side effect follows, and the parameter note is short. Slightly telegraphic phrasing ('(when automatic)') costs a little clarity but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a stateful, potentially mutating tool with no annotations and no output schema, so the description should say more about outcomes. It never describes what statuses are returned, what a timeout or rejection looks like, or whether re-polling is safe, which leaves an agent unable to interpret the result.

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 description coverage is 0%, so the description must compensate. It does explain wait_seconds well (blocking up to a max of 50 for the user's decision), but request_id, the required parameter, gets no explanation at all.

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 states a specific verb and resource: 'Check an install or uninstall request,' and adds that it may 'start the work' if the user approved. That is clearly distinct from initiation siblings like request_install, though it never names them explicitly.

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 'If the user approved it' clause hints that this is polled after a prior approval request, and 'when automatic' hints at a conditional mode. There is no explicit when-to-use, when-not-to-use, or alternative named.

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