Skip to main content
Glama
Sign In

Privi Ledger

by io.github.canoydario847-cloud
OverviewDiscussionsAdmin

KYA: bind a wallet

kya_bind_wallet
Idempotent

Step 2: bind the wallet to your organization's Privi Passport so its transactions pass KYA checks. With a wallet signature the binding is proven; without one it is only declared (most checkers require proven). Requires the organization API 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": {
      "address": "<address>"
    },
    "name": "kya_bind_wallet"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelNoFriendly name, e.g. 'treasury-agent hot wallet'
addressYes0x wallet address
signatureNo65-byte hex signature of the challenge message by the wallet
stream_idNoThe agent (stream) that uses this wallet; omit for the whole organization
challenge_idNoFrom kya_challenge

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare the safety profile (readOnly=false, destructive=false, idempotent=true, openWorld=false), so the description's added value is the semantic consequence of the signature parameter (proven vs merely declared) and the auth requirement. It does not disclose error behavior or whether re-binding an already-bound wallet is a no-op, but the annotation coverage lowers the bar.

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 tight sentences, front-loaded with the action and purpose, then the signature distinction, then the auth prerequisite. No filler or repetition of the schema.

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 5-parameter mutation tool with no output schema and no enums, the description covers purpose, prerequisite, and the key behavioral distinction, while the schema handles the stream_id/label/challenge_id scoping. It could say more about failure modes or what is returned, but nothing essential to correct invocation is missing.

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; the description earns an extra point by explaining what the signature parameter actually accomplishes in the domain (proof vs declaration and why checkers care), which is meaning the schema's mechanical '65-byte hex signature' text does not convey.

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 ('bind the wallet to your organization's Privi Passport') plus the outcome it enables ('transactions pass KYA checks'), and its 'Step 2' framing plus the bind/unbind sibling names let an agent place it precisely in the KYA family.

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?

Gives clear conditions for the two modes ('with a wallet signature the binding is proven; without one it is only declared (most checkers require proven)') and states the prerequisite 'Requires the organization API key'. It stops short of explicitly naming kya_challenge as the prerequisite call or ruling out alternatives, but the context for when to call it is clear.

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

All Privi Ledger toolsInspect
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