Skip to main content
Glama
Sign In

DebitMyData Agentic Superhighway

by io.debitmydata
OverviewDiscussionsAdmin

Purchase quote options

dmd_get_purchase_quote
Read-only

The commercial price (or a donation's amount range) and the supported currencies and wallets for one product. Use dmd_purchase to buy it or to donate.

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": {
      "product_id": "<product_id>"
    },
    "name": "dmd_get_purchase_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_idYesProduct ID from dmd_catalog

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare this as read-only and closed-world, and the description reinforces that it only returns quote information while dmd_purchase handles the transaction. Beyond that it does not disclose whether quotes expire, are real-time, or have other behavioral constraints; with the output schema covering returns, a 3 is appropriate.

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 with no wasted wording; the returned information is front-loaded and the follow-up action is stated immediately after. The parenthetical donation range is compact and informative.

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 one-parameter, read-only quote lookup with an output schema and annotations, the description supplies what is returned and which sibling handles the purchase. A little more guidance on when a quote should be fetched (e.g., before purchase) would make it fully complete, but nothing critical 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?

The only parameter is fully documented in the schema as a product ID from dmd_catalog, and the description adds little beyond saying the quote is for one product. With 100% schema coverage, the 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?

The description identifies the returned data (commercial price or donation range, supported currencies, and wallets) for a single product, so the resource is clear. It does not open with an explicit verb like 'retrieve,' but the name/title and the contrast with dmd_purchase make the purpose understandable.

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?

It explicitly routes purchasing/donating to dmd_purchase, which acts as a when-not boundary for this read-only quote tool. It does not explicitly say 'call this before purchasing' or distinguish from other payment-option listing tools, so it is not a full 5.

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