Skip to main content
Glama

aamio_scope_add

Idempotent

Store a scope created elsewhere under a name by supplying its read/post key or write-only address, enabling later reuse without recreating it.

Instructions

Keep a scope made elsewhere under a name: the key to read and post, or the address to post only. A key given here has passed through this conversation, so a scope shared from runtime to runtime with aamio_scope_share is better, since that never shows the key.

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

Input Schema

NameRequiredDescriptionDefault
keyNo26 to 64 characters of a-z and 0-9
nameYes
addressNothe 20 characters that go on a post

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.32

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive, open-world, so the description is not obligated to restate safety. It contributes real context beyond them: the security tradeoff of a key passing through conversation history, and the privilege difference between a key (read + post) and an address (post only). What it omits is what happens when the name already exists and what the call returns.

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?

Two sentences, no filler, and the core semantics (key vs address) are front-loaded before the recommendation to use a sibling. The phrasing "the key to read and post, or the address to post only" is compact but slightly convoluted on first read.

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?

There is no output schema, so the description should carry the full burden, yet it never says what a successful add produces or how name collisions behave despite idempotentHint=true. It covers the what, the credential semantics, and the preferred alternative, which is adequate for a three-parameter tool, but the naming/collision behavior is a real gap.

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 67%, and the description fills the functional gap the schema leaves: it explains what each credential grants (key = read and post, address = post only) rather than just echoing the field descriptions. The name parameter's meaning (a local handle for the stored scope) is only implied by "under a name".

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?

"Keep a scope made elsewhere under a name" states a specific action (register/persist an externally created scope) plus the two credential forms it accepts — key (read and post) or address (post only). That is enough for an agent to tell it apart from aamio_scope_share, which it names explicitly. It stops short of 5 because the invented vocabulary ("scope", "address") and the indirect verb "keep" require domain familiarity.

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?

It gives an explicit alternative with a condition and rationale: when the scope travels runtime-to-runtime, use aamio_scope_share instead because the key never appears in the conversation. The phrase "made elsewhere" also implicitly separates it from a scope creation sibling. It does not spell out the inverse case (when you must use this tool, e.g. copying from a message or config), leaving part of the routing to inference.

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