Skip to main content
Glama

Marketplace provider requirements

dmd_marketplace_provider_requirements
Read-only

What an agent needs in order to sell through DebitMyData.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the agent knows this is a self-contained read. The description adds conceptual framing (seller-side requirements) but says nothing about what the response contains or how it should be acted on. With annotations and an output schema in place, a 3 reflects modest added value rather than a gap.

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 short sentence with no filler and the concept front-loaded. It is efficient, though the terseness borders on under-specification rather than true crispness.

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?

For a zero-parameter, read-only lookup with an output schema, the description is minimally sufficient to know roughly what the tool covers. It still omits what the requirements consist of and when in the seller workflow to call it, which matters for an agent sequencing marketplace steps.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter semantics for the description to explain and the baseline of 4 applies. The empty schema means nothing is left ambiguous about inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The sentence 'What an agent needs in order to sell through DebitMyData' conveys the subject matter (provider/seller requirements) but supplies no explicit verb such as 'returns' or 'lists', so the agent must infer that this is a lookup of onboarding/selling requirements. It largely restates the title rather than differentiating from siblings like dmd_catalog or dmd_discover, which could plausibly also describe what an agent needs.

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 when-to-use guidance, no prerequisites, and no indication of an alternative tool to consult instead. The only implicit cue is the word 'sell', leaving the agent to guess whether to call this before dmd_purchase or dmd_register_did.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.