Skip to main content
Glama

aamio_scope_remove

DestructiveIdempotent

Forgets a scope on the local machine; its posts remain on the board until they expire, and other key or address holders keep their copies.

Instructions

Forget a scope on this machine. Its posts stay on the board until they expire, and everyone else holding its key or address keeps 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": {
      "name": "<name>"
    },
    "name": "aamio_scope_remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.32

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, but the description adds the critical nuance that the destruction is local-only: posts persist on the board until expiry and other holders of the key/address are unaffected. That materially recalibrates how aggressively an agent should treat a "destructive" call. It does not address reversibility (whether the scope can be re-added) or any auth requirement.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no waste; the local-scope constraint is front-loaded and the side effects follow immediately.

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?

For a destructive one-parameter tool the side-effect disclosure is good, but the definition omits what the call returns or confirms, whether the scope can be recovered by re-adding, and what identifier form 'name' accepts. These gaps matter given a mutation with no output schema.

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?

The single required parameter 'name' has 0% schema description coverage, so the description must compensate. It refers to a scope's "key or address", which hints at acceptable identifier forms, but never states that the name argument is that identifier nor any naming format.

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?

"Forget a scope on this machine" gives a concrete verb (remove/forget) and resource (scope) plus an important locality qualifier, and the follow-up sentence clarifies that removal is local rather than global. It stops short of explicitly contrasting with aamio_scope_add / aamio_scope_share, but the intent is unmistakable.

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: an agent can infer you call this when this machine should stop tracking a scope, and the second sentence hints at the consequence of doing so. No explicit when-to-use, when-not, or named alternative is provided.

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