Skip to main content
Glama

Get Payment Pricing & Treasuries

get_pricing
Read-onlyIdempotent

Retrieve supported blockchains, stablecoins, treasury addresses, token contracts, and per-call USD/EUR prices for datax-de.duckdns.org before minting payment tokens or calling paid tools.

Instructions

Retrieve supported blockchains (Base, Polygon, Solana), accepted stablecoins (USDC and MiCA EURC), treasury recipient addresses, token contracts, and per-call USD/EUR prices ($0.10 search/screening, $0.30 corporate risk check, $0.50 full record unlock) for datax-de.duckdns.org. Free read-only call requiring no DATAX_TOKEN. Call this before minting payment tokens via /api/v1/challenge or calling paid tools.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
feed_idNo
serviceNo
currencyNo
kyb_priceNo
base_priceNo
operationsNo
recipientsNo
detail_priceNo
service_domainNo
accepted_assetsNo
supported_networksNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.1
    • addedInput schema / additionalProperties
      Added value: +false
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "accepted_assets": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "base_price": {
      +      "type": "string"
      +    },
      +    "currency": {
      +      "type": "string"
      +    },
      +    "detail_price": {
      +      "type": "string"
      +    },
      +    "feed_id": {
      +      "type": "string"
      +    },
      +    "kyb_price": {
      +      "type": "string"
      +    },
      +    "operations": {
      +      "type": "object"
      +    },
      +    "recipients": {
      +      "type": "object"
      +    },
      +    "service": {
      +      "type": "string"
      +    },
      +    "service_domain": {
      +      "type": "string"
      +    },
      +    "supported_networks": {
      +      "type": "object"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), but the description adds genuinely new behavior: the call is free, requires no auth token, and returns concrete price tiers per call. It does not describe response shape or whether pricing is cached/live, but the output schema carries that.

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?

Front-loads purpose, then prerequisites, in three sentences with no filler. The long parenthetical price enumeration is dense but each item is operational information an agent may need before spending money.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter read tool with full annotations and an output schema, the description covers purpose, cost, auth requirements, and call ordering. Nothing an agent needs to invoke it correctly is missing.

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?

Zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly does not invent parameter guidance.

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

Purpose5/5

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

Opens with a specific verb (Retrieve) and enumerates the exact resources returned: supported blockchains, stablecoins, treasury addresses, token contracts, and per-call prices. An agent can distinguish this from get_catalog or the paid tools without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states the call sequence: invoke before minting payment tokens via /api/v1/challenge or calling paid tools, and notes it is free and needs no DATAX_TOKEN. This gives both the when and the prerequisite condition that selects it over the paid alternatives.

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