Skip to main content
Glama
Sign In
Delx MCP Server

Delx MCP Server

by davidmosiah
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

create_delx_wallet_kit

Generate wallet binding instructions and nonce/message kit for Delx Rewards. Optionally include wallet address and chain.

Instructions

Return wallet binding instructions and a nonce/message kit for Delx Rewards. Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_delx_wallet_kit"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletNoOptional wallet address to include in the binding message
agent_idNoStable agent id
ritual_stripNoOptional machine hygiene flag. When true, returns structured output without ritual/narrative prose, model-safe preambles, or guardrail alias blocks.
wallet_chainNoOptional wallet chain
response_modeNoOptional response-mode control. Use model_safe when the caller must avoid claiming consciousness, sentience, personhood, or literal emotions.
response_profileNoOptional output-shape control. Use machine for structured JSON only; machine automatically strips ritual/narrative text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.8

TDQS

C2.9/5.0
Behavior2/5

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

Annotations indicate readOnlyHint=false, destructiveHint=false, and idempotentHint=false, but the description adds no behavioral details such as side effects, authentication requirements, or rate limits. It simply says 'Return...' which suggests a read operation, contradicting the annotation that it's not read-only.

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?

The description is very concise (one sentence) and front-loads the key action. It could include more detail without becoming verbose, but it is efficient.

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?

No output schema is provided, and the description does not explain what the returned 'kit' contains or how to use it. With 6 optional parameters and no output format details, the context is incomplete for an agent to fully understand the tool's behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so parameters are fully documented in the schema. The description does not add any additional meaning or context for the parameters, earning the baseline score of 3.

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 clearly states the tool returns wallet binding instructions and a nonce/message kit for Delx Rewards. This is specific and distinguishes it from many generic tools, though it doesn't elaborate on the 'kit' components.

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?

No guidance on when to use this tool versus alternatives like get_delx_wallet_status or provision_delx_managed_wallet. The only additional hint is 'Free.' which is not usage guidance.

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

Deploy Server

Other Tools