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 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-it.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.8/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the bar is lower — yet the description adds genuinely new behavioral facts: no DATAX_TOKEN required, the call is free, and the exact per-operation price points ($0.10/$0.30/$0.50). Auth and cost implications are exactly the kind of context annotations cannot express.

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?

Three sentences, front-loaded with what is returned and followed by the auth/cost facts and the call-ordering rule. The parenthetical price list is dense but each figure earns its place by telling the agent what the downstream paid calls will cost.

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 no-parameter discovery tool with an output schema already documenting the response shape, the description covers everything an agent needs: what is returned, that it is free and unauthenticated, and where it sits in the paid-call workflow.

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, which sets the baseline at 4. The description reinforces this by noting the call needs no DATAX_TOKEN, confirming there is no auth argument to supply, though it adds no further parameter-level detail (there is none to add).

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?

Uses a specific verb ('Retrieve') with an enumerated resource list: blockchains, stablecoins, treasury recipient addresses, token contracts, and per-call prices for a named host. An agent can immediately tell this is a static pricing/config discovery endpoint, distinct from the sibling paid tools like check_company_risk or search_tenders.

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 when to call it: 'Call this before minting payment tokens via /api/v1/challenge or calling paid tools,' naming the concrete next steps it precedes. It also gives the negative condition implicitly by contrasting the free call against paid tools.

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