Skip to main content
Glama

Get prices

get_quote
Read-onlyIdempotent

Use before create_proof to see what a proof will cost right now. Proof $1 + network fee, no API key. Current prices for every proof type. Each is a flat USD service fee plus the Bitcoin network fee on top: proof $1, publication $1, deed (Ownership Token) $1, artwork (Certificate of Provenance) $1. Returns the service fee in USD and sats, the address it is paid to, current network fee rates (sat/vB, never below 5) and an estimated network fee. Read-only; nothing is reserved.

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_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkNoDefault mainnet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the description does not need to carry the full safety burden. It still adds useful behavior: no API key is required, nothing is reserved, prices are flat USD service fees plus a network fee, and the network fee rate is never below 5 sat/vB.

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 description is front-loaded with the main use case and remains readable. It does repeat the proof pricing point and then enumerates each proof type at $1, which is slightly verbose but still useful for pricing clarity.

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 one-parameter read-only pricing tool with full schema coverage and no output schema, the description is complete. It explains what is returned, including service fees in USD and sats, the payment address, network fee rates, and an estimated network fee.

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

Parameters3/5

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

Schema description coverage is 100%, so the single network parameter, its enum values, and its default are already fully documented in the schema. The description does not add any parameter-specific meaning, so the baseline of 3 is appropriate.

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 states a specific verb and resource: it returns current prices for every proof type, including the service fee and Bitcoin network fee. It also names the sibling create_proof and places itself in that workflow, making the purpose distinguishable without needing to open 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 Guidelines4/5

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

It gives explicit when-to-use guidance: use before create_proof to see the current cost. It does not state when not to use it or discuss alternatives, but the intended workflow is clear enough for an agent.

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.