Xaalis

Issue an agent wallet key (sandbox)

xaalis_issue_agent_key

Idempotent

Sandbox: issue the ak_test_ key an agent uses to pay out from this wallet. The secret is shown ONCE — store it in a secret store or env var right away. Retrying with the same idempotency_key never shows it again.

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": {
      "wallet_id": "<wallet_id>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "xaalis_issue_agent_key"
  }
}

Input Schema

Name	Required	Description	Default
`wallet_id`	Yes	Agent wallet id (aw_…)
`idempotency_key`	Yes	Stable key for this business action (e.g. order-1042). Reuse the SAME key when retrying; a new key creates a new operation.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 1, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Goes well beyond the annotations: the secret is shown ONCE and must be stored immediately, and a retry with the same idempotency_key will never surface it again. That is the single most consequential behavior for this tool and is not derivable from idempotentHint/destructiveHint alone.

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?

Three short sentences, zero waste, with the sandbox scope and the one-time-secret warning front-loaded before the retry caveat.

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

Completeness5/5

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

Only two parameters, both fully documented in schema, rich annotations, and no output schema to explain. The description covers the one non-obvious operational hazard (credentials not retrievable after the first response), which is exactly what an agent needs before calling.

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 100%, so the baseline is 3, but the description adds a real semantic consequence of idempotency_key — that reuse suppresses re-display of the secret, not just duplicate operations. wallet_id itself is left to the schema, which is fine given its documented aw_ prefix.

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?

States a specific verb and resource ('issue the ak_test_ key an agent uses to pay out from this wallet') plus the sandbox scope. An agent can immediately tell this apart from create_agent_wallet, fund_agent_wallet, and get_agent_wallet without opening any schema.

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?

Clear context: sandbox-only, requires an existing agent wallet, and explicit retry behavior with the same idempotency_key. It does not name a prerequisite sibling (e.g. call create_agent_wallet first) or state when not to use it, so it stops short of full routing guidance.

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

All Xaalis tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?