Skip to main content
Glama

get_resolve_price_threshold

Read-only

Resolve whether a crypto asset is above or below a threshold via multi-source consensus for settlement and verification workflows. $0.50 USDC per call.

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": {
      "symbol": "<symbol>",
      "threshold": "<threshold>",
      "direction": "<direction>"
    },
    "name": "get_resolve_price_threshold"
  }
}

Input Schema

NameRequiredDescriptionDefault
fiatNousd
symbolYes
directionYes
thresholdYes
tolerance_pctNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing the consensus mechanism and the $0.50 USDC per-call cost, but it omits what the result looks like and how ties/tolerance are handled.

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 tight sentences with the purpose front-loaded and the price disclosure clearly appended. Nothing is wasted, though the brevity borders on under-specification rather than genuine concision.

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 five-parameter, no-output-schema tool whose core ambiguity is boundary handling via tolerance_pct, the description leaves key semantics and the return shape entirely unaddressed. It is too thin relative to the tool's complexity.

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?

Schema description coverage is 0% across five parameters, so the description is the only source of parameter meaning — yet it says nothing about symbol, threshold, direction, fiat, or tolerance_pct (including the 0.5 default and its role in boundary cases). It fails to compensate for the coverage gap.

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?

The description names a specific verb+resource: resolving whether a crypto asset is above or below a threshold, and explains the mechanism (multi-source consensus). It is clearly distinct from list-style siblings, but it never names a sibling such as get_verify_crypto_price, so the differentiation is implicit.

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

Usage Guidelines3/5

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

"for settlement and verification workflows" gives a usage context, which is more than nothing. However, there are no explicit when-not conditions and no comparison to alternative price tools, so an agent must infer boundaries.

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.

Resources