Skip to main content
Glama

aqb_announce_stealth

Publish a stealth address from a PQSmartAccount so a payer can receive private transfers. Share the ephemeral public key and shared secret to announce the payment on-chain.

Instructions

Publish a stealth address for a payer from a PQSmartAccount

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": {
      "account": "<account>",
      "ephPubKey": "<ephPubKey>",
      "sharedSecret": "<sharedSecret>"
    },
    "name": "aqb_announce_stealth"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountYes
metaHashNo
ephPubKeyYes
sharedSecretYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries full burden, yet "Publish" leaves the side-effect profile opaque: it is unclear whether this registers something on-chain, whether it costs funds, whether it is idempotent, or what a caller gains afterward. Key mechanics such as the shared secret's role and any privacy implications are unaddressed.

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?

A single front-loaded sentence with no filler or redundancy. It is efficiently written, though its brevity is under-specification rather than true economy given the domain's complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter cryptographic tool with no annotations, no output schema, and zero schema documentation, the description is far too thin. An agent cannot determine required inputs' meaning or the observable outcome of calling it.

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% across four parameters, so the description must compensate and does not. Only a weak link is implied between "account" and "PQSmartAccount"; ephPubKey, sharedSecret, and especially the optional metaHash are left completely unexplained, including formats and encoding.

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?

The description gives a specific verb and resource ("Publish a stealth address") plus the target ("for a payer from a PQSmartAccount"), which distinguishes it from transactional siblings like aqb_pay or aqb_fund. It stops short of explicitly contrasting itself with any named alternative.

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

Usage Guidelines2/5

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

There is no guidance on when this should be called, no prerequisites stated (e.g. whether the payer or account must already be registered or funded), and no mention of alternatives. The agent must infer the workflow entirely.

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