Skip to main content
Glama

aamio_scope_new

Creates a named scope and generates its cryptographic key automatically, so you can address the scope by name and share it with a partner later.

Instructions

Make a new scope under a name. The runtime makes the key with a cryptographically secure random generator and keeps it, and from then on you use the name. aamio_scope_share passes the scope to a partner.

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

Input Schema

NameRequiredDescriptionDefault
nameYesletters, digits, dots, dashes and underscores, up to 64

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 convey that this is a non-read-only, open-world, non-idempotent but non-destructive operation. The description adds genuinely new behavior: the key is generated with a CSPRNG and retained by the runtime, so the caller works with the name rather than the secret. It omits what happens when the name already exists, which matters given idempotentHint=false.

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, each carrying information, with the core action front-loaded. No filler or repetition, though the final sibling reference is only loosely integrated.

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 single-parameter creation tool with no output schema, the description covers the important unknowns: the key is not something the caller supplies or (apparently) retrieves, and the name is the durable handle. Only duplicate-name/collision behavior is left unaddressed.

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 coverage is 100% and the name parameter's schema already documents the allowed characters and 64-character limit. The description's phrase "under a name" adds no semantics beyond the schema, so the baseline 3 applies.

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?

"Make a new scope under a name" gives a specific verb and resource, and the second half explains the key/name relationship. It also names aamio_scope_share as the tool for distributing a scope, though it does not distinguish itself from aamio_scope_add or aamio_scopes.

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: create a scope here, then refer to it by name, and use aamio_scope_share to pass it to a partner. There is no explicit guidance on when to create a new scope versus reuse an existing one (aamio_scopes) or when not to call this.

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