Kivel MCP Server

create_test_wallet

Create a workspace wallet with fake USD test units. Test mode only: no real funds, blockchain or private keys. Agent keys receive plan defaults for limits and approval thresholds; only a human owner/admin can change them. Counts toward resource limits.

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": "create_test_wallet"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`balance`	No
`persistent`	No
`ttlSeconds`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already declare a non-destructive, closed-world create, and the description adds meaningful context on top: no real funds, blockchain or private keys, agent keys inherit plan defaults, humans must change thresholds, and creation consumes resource limits. The main omission is any statement about what the call returns or what happens on duplicate names.

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?

Four short, front-loaded sentences with no filler; the mode and safety constraints come before the governance detail. It is dense but readable, and nothing reads as wasted boilerplate.

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?

Behavioral and safety context is strong for a create tool, but with four undocumented parameters, no output schema, and an unclear persistence/TTL interaction, an agent still lacks what it needs to fill the optional fields correctly.

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, and the description mentions none of them by name. The non-obvious fields, particularly 'persistent' versus 'ttlSeconds' and what 'balance' controls in test units, are left entirely unexplained, so the definition does not compensate for the schema gap.

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 names a specific verb and resource ('Create a workspace wallet') and pins the scope ('fake USD test units'), which separates it from real-money wallet operations and from siblings such as create_test_checkout. It stops short of naming a sibling alternative explicitly, so differentiation is implied by the 'wallet' resource rather than stated.

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?

'Test mode only' is a real usage boundary, and the note that only a human owner/admin can change limits tells the agent who is in control. There is no explicit guidance on when to pick this over a checkout/paywall sibling, and no when-not-to-call guidance beyond the test-mode constraint.

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

All Kivel MCP Server 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?