Skip to main content
Glama

get_quote

Retrieves the current price for a paid data feed in sats and USD, including token lifetime, so you can check access costs before subscribing. Free feeds never incur payment.

Instructions

Current price of a paid feed (sats, USD, token lifetime). Free; never pays.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "feed": "<feed>"
    },
    "name": "get_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
feedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the call is free and never pays, but does not state read-only behavior, permissions, rate limits, side effects, or output structure.

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?

Two short fragments with the core purpose front-loaded and no filler. 'token lifetime' and 'Free; never pays' are terse and somewhat ambiguous, but not verbose.

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

Completeness2/5

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

For a one-parameter read tool with no annotations and no output schema, the definition omits feed format details and does not clarify what 'token lifetime' means or how the quote is returned. It is simple but not complete enough for reliable invocation.

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

Parameters2/5

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

The single required 'feed' parameter has 0% schema description coverage. The description only calls it a 'paid feed' and does not explain identifier format, accepted values, or how to obtain a valid feed reference.

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

Purpose4/5

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

States that the tool returns the current price of a paid feed and names the units (sats, USD, token lifetime). The resource is specific, but sibling differentiation from list_feeds or fetch is not made explicit.

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

Usage Guidelines2/5

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

Provides no when-to-use or when-not-to-use guidance and does not name alternatives such as list_feeds or fetch. 'Free; never pays' is cost information, not routing guidance.

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

Deploy Server

Other Tools