DebitMyData Agentic Superhighway

Create a DID-LLM payment quote

dmd_create_did_payment_quote

Create a time-limited quote: the fixed 25.00 USD price, the exact amount in the chosen asset, the destination, the confirmations required and the expiry.

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": {
      "display_name": "<display_name>",
      "participant_type": "<participant_type>",
      "preferred_payment_option": "<preferred_payment_option>"
    },
    "name": "dmd_create_did_payment_quote"
  }
}

Input Schema

Name	Required	Description
`metadata`	No	Optional small key/value metadata (up to 20 keys)
`display_name`	Yes	Public name of the agent
`idempotency_key`	No	Optional random key (16-128 characters, e.g. a UUID); retrying with the same key returns the same quote
`participant_type`	Yes	What kind of participant
`controller_network`	No	The wallet's network, e.g. eip155:8453 for Base (the default)
`controller_public_key`	No	Ed25519 public key that will control the DID-LLM: ed25519:z6Mk..., or ed25519: followed by 64 hex characters or base64. Give this, a wallet, or both.
`preferred_payment_option`	Yes	Payment option ID from the offer, e.g. dmd_pow_native
`controller_wallet_address`	No	EVM wallet that will control the DID-LLM: 0x... (checksummed or all lower case) or eip155:<chain id>:0x.... Its control is proven like the key's, by signing a challenge (smart wallets included).

Output Schema

Name	Required	Description	Default
No arguments

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 declare a non-destructive, closed-world write, and the description adds real context beyond them: the price is fixed at 25.00 USD, the quote is time-limited with a stated expiry, and it fixes the required confirmations. It does not disclose whether the quote is persisted server-side or mention idempotency behavior, but the added detail is substantive.

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 a compact colon list; every element maps to something the quote actually contains. Minor redundancy in spelling out the quote contents, but no filler.

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?

An output schema exists, so return values need no explanation. However, for a mutation tool that opens a multi-step payment flow, the description omits prerequisites and next steps (offer lookup, payment submission), leaving the agent to infer the sequence.

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 already documented, and the description merely gestures at some of them ('chosen asset', 'destination', 'confirmations'). It adds no meaning about the controller key vs. wallet choice or the idempotency key beyond what the schema already says; baseline 3 applies.

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?

States a specific verb and resource ('Create a ... quote') and enumerates what the quote contains (fixed price, asset amount, destination, confirmations, expiry). It is clear what the tool produces, though it never names a sibling (e.g. dmd_get_purchase_quote or dmd_get_did_registration_offer) to disambiguate the quote types.

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 explicit when-to-use guidance, no prerequisites (such as obtaining preferred_payment_option from an offer first), and no mention of where this fits in the purchase flow or which sibling it replaces. The flow is only implied by the word 'quote'.

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

All DebitMyData Agentic Superhighway 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.