Skip to main content
Glama
Sign In

DebitMyData Agentic Superhighway

by io.debitmydata
OverviewDiscussionsAdmin

Submit a payment reference

dmd_submit_payment_reference
Idempotent

Report the transaction that pays a quote. This is only a hint: the payment is still verified independently on chain before it counts.

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": {
      "payment_intent_id": "<payment_intent_id>",
      "transaction_reference": "<transaction_reference>"
    },
    "name": "dmd_submit_payment_reference"
  }
}

Input Schema

NameRequiredDescriptionDefault
payment_intent_idYespayment_intent_id from the quote (dmd_payment_intent_...)
transaction_referenceYesTransaction ID / hash of the payment you broadcast

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations, the description discloses the critical behavioral trait: the submitted reference is 'only a hint' and payment is verified independently on chain before counting. That tells an agent the call does not immediately settle the quote. It does not say how long verification takes or how to observe the outcome, which keeps it from a 5.

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?

Two short sentences, front-loaded with the action and immediately followed by the most important caveat. No repetition of the title, no filler.

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?

An output schema exists, so return values need not be explained, and the two-parameter surface is fully documented in the schema. The description covers purpose plus the non-obvious verification caveat; it could add how the agent learns the verification result, but nothing essential for invoking it correctly is missing.

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 both parameters are already documented with the exact pattern and expected format. The description adds only loose linkage ('the transaction that pays a quote') that maps to transaction_reference and the quote's payment_intent_id, so baseline 3 is appropriate.

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 uses a specific verb+resource pair ('Report the transaction that pays a quote'), making clear this submits a payment transaction reference rather than querying status. It does not explicitly name a sibling such as dmd_get_payment_status as the alternative for checking whether payment landed, so it stops short of a 5.

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?

Usage is only implied: you call it after broadcasting a payment for a quote. There is no explicit when-to-use, no statement about what to do if the reference was already submitted (the idempotent annotation covers this but the text does not), and no routing to sibling tools for status checks.

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 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