Skip to main content
Glama

Get Payment Pricing & Treasuries

get_pricing
Read-onlyIdempotent

Retrieve supported blockchains, stablecoins, treasury addresses and per-call USD/EUR prices before paying for data. Free read-only call to check costs first.

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-es.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.2
    • 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 (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint), so the description's real value-add is the auth and cost context: it states the call is free and requires no DATAX_TOKEN, which is not expressed anywhere in the annotations. It stops short of disclosing rate limits, price staleness, or caching behavior, which keeps it at 4 rather than 5.

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?

The payload enumeration in the first sentence is dense but every item is a distinct returned field the caller needs (chains, coins, addresses, contracts, prices). The actionable prerequisite sentence is placed at the end rather than front-loaded, which is the only structural weakness.

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?

The definition covers the returned domain, the cost model with concrete per-call figures, the auth requirement, and the prerequisite ordering, which is everything an agent needs to invoke a parameterless pricing endpoint correctly. An output schema exists, so the description is not obliged to restate the response shape, and it doesn't.

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 the schema-completeness baseline of 4 applies; there is no parameter semantics to elaborate. The description correctly avoids inventing inputs and instead spends its words on the returned data contract.

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?

The description opens with a specific verb (Retrieve) and then enumerates exactly what is returned: supported blockchains, stablecoins, treasury recipient addresses, token contracts, and per-call USD/EUR prices. It also anchors the resource to a concrete endpoint (datax-es.duckdns.org), so an agent can distinguish this pricing/bootstrap tool from the search and risk siblings without opening a 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?

It gives explicit sequencing: 'Call this before minting payment tokens via /api/v1/challenge or calling paid tools.' That is both a when-to-use rule and a named downstream alternative, which is the strongest form of routing guidance in this dimension.

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