Skip to main content
Glama

Get Payment Pricing & Treasuries

get_pricing
Read-onlyIdempotent

Retrieve supported blockchains, stablecoins, recipient addresses, token contracts, and per-call USD/EUR prices before minting payment tokens or calling paid data 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-pt.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.4/5.0
Behavior4/5

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

Adds context beyond the annotations by disclosing that the call is free and requires no DATAX_TOKEN, which is the key operational fact for an agent deciding whether it can call this now. Pricing and treasury-address contents further describe outcomes, and the annotations already cover read-only/idempotent/non-destructive semantics; only pagination or response-shape detail is absent, and an output schema exists.

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 the resource list and ends with the actionable prerequisite, and every clause carries concrete detail (chains, stablecoins, prices, token contract) rather than filler. The single long enumeration is dense but readable; it could be split for scannability but nothing is wasted.

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-only discovery tool with an output schema and full annotations, the description supplies everything an agent needs: what comes back, that it is free and unauthenticated, and that it must be called before payment-gated tools. No meaningful gap remains.

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 schema takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies the call needs no inputs, consistent with the empty object schema.

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?

States a specific verb ("Retrieve") and enumerates exactly what is returned: supported blockchains, accepted stablecoins, treasury recipient addresses, token contracts, and per-call prices. An agent can distinguish this catalog/pricing tool from siblings like get_catalog or check_company_risk without opening any schema.

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?

Explicitly instructs "Call this before minting payment tokens via /api/v1/challenge or calling paid tools," which gives a clear ordering constraint that selects this tool over the paid siblings. It does not state when not to call it or name sibling alternatives, so it stops short of the top band.

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