Skip to main content
Glama

aamio_scope_share

Share a scope with an address-book partner through a sealed, signed message: grant read plus post access, or write-only posting, without exposing the key in chat.

Instructions

Share one of your scopes with a partner in a sealed and signed message. access read gives the key, so the partner can read and post. access write gives only the address, so the partner can post without reading. It goes only to a partner in your address book, never to an address, whoever asks for it. The key never appears in this conversation, and the partner's runtime keeps the scope under your name and the scope's when the message comes sealed from someone in its address book.

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>",
      "to": "<to>",
      "access": "<access>"
    },
    "name": "aamio_scope_share"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesa partner name
nameYes
accessYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.32

TDQS

A4.1/5.0
Behavior4/5

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

With annotations declaring destructiveHint=false and only a generic openWorldHint=true, the description adds the security-relevant behavior that matters: the key is included only in sealed transit, never in this conversation, and the recipient keeps the scope under the sender's name. That disclosure goes well beyond structured fields. It omits whether sharing can be revoked or what error appears when the partner is unknown, and the final sentence is hard to parse.

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

Conciseness3/5

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

Content is dense and valuable, but it arrives as three long run-on sentences, and the last one ('keeps the scope under your name and the scope's when the message comes sealed...') is grammatically tangled enough to slow comprehension. The read/write contrast, the most actionable part, is buried in the middle.

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 3-parameter mutation with no output schema, the core semantics are covered: recipient restriction, access-mode meaning, and secret handling. Missing are the failure mode for a non-address-book partner, whether a share can be undone, and any hint of what a successful share returns.

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 only 33%, so the description carries much of the burden: it fully defines access=read versus access=write in behavioral terms, and links 'to' to the address-book partner-name constraint beyond the schema's bare 'a partner name'. The 'name' parameter, which scope is being shared, is only implied by 'one of your scopes'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource (share a scope), plus the delivery mechanism (sealed and signed message) and the recipient constraint (a partner in your address book). An agent can distinguish this from aamio_scope_add/new/remove, which manage scopes locally, rather than share them outward.

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 explains both modes of use: 'access read gives the key, so the partner can read and post' versus 'access write gives only the address, so the partner can post without reading', which is a genuine decision rule for the enum. It also states a hard precondition, that it works only for a partner in the address book and never for a bare address. It does not name a sibling alternative or state what to do when that precondition fails.

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