Skip to main content
Glama

request_uninstall

Requests user approval to remove a Brigse-installed add-on; nothing is deleted immediately. Poll install_status with the returned request_id to track approval and removal progress.

Instructions

Ask the user to approve removing an add-on that Brigse installed. Nothing is deleted by this call.

Only add-ons installed by Brigse can be removed (the downloaded open-source tools); vendor tools the user installed are never touched. Poll install_status with the returned request_id.

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

Input Schema

NameRequiredDescriptionDefault
reasonNo
backendYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 does well on the most important point: 'Nothing is deleted by this call,' clarifying this is a request, not the mutation itself, plus the guardrail that vendor tools are never touched. It leaves out what happens on denial or timeout, whether approval is asynchronous, and any permission requirements, which matter for an approval-gated operation.

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, front-loaded with the action and immediately followed by the safety reassurance. The parenthetical clarifying what 'Brigse add-ons' means earns its space; little is wasted.

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?

Covers the action, the safety profile, the eligibility rule, and the follow-up polling step, and notes the returned request_id in lieu of an output schema. The unresolved gap is parameter meaning for a tool with zero schema descriptions, which leaves an agent guessing what to pass as 'backend'.

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 explain the two parameters, and it explains neither. 'backend' (required) is never defined, nor is what 'reason' is used for or who sees it. The only identifier mentioned, request_id, is an output, not an input.

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?

States a specific verb and resource ('ask the user to approve removing an add-on') and bounds the scope to add-ons Brigse installed. An agent knows exactly what the call initiates, though it never names request_install as the counterpart, so the install/uninstall pairing must be inferred from the sibling list.

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

Usage Guidelines4/5

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

Gives explicit sequencing: call this first, then poll install_status with the returned request_id. It also states the eligibility condition (only Brigse-installed add-ons). It stops short of saying when not to use it or what to do if the user declines.

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