Skip to main content
Glama

Price

get_price
Read-only

Current spot or USDⓈ-M perpetual last price (market spot by default, or futures). Free.

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>",
      "market": "<market>"
    },
    "name": "get_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
marketYesspot
symbolYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, covering safety and external-data behavior. The description adds that the data is current and free, plus the market default, but does not disclose update frequency, latency, or authentication expectations.

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 definition is a single front-loaded sentence with no wasted framing. The parenthetical market note is somewhat redundant with the schema default, but overall the structure is tight.

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

Completeness3/5

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

For a simple two-parameter tool with no output schema, the description is mostly sufficient: it identifies the returned price and market behavior. However, it omits symbol formatting guidance and does not clarify return shape beyond 'last price', leaving a meaningful gap for 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?

Schema description coverage is 0%, so the description must carry the burden. It explains the market enum and default, which are already in the schema, but leaves the required symbol parameter entirely undefined in terms of expected format or examples.

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 clearly states the tool retrieves the current last price for spot or USDⓈ-M perpetual markets. It is specific about the resource but does not explicitly differentiate this from siblings such as market_context or get_analysis.

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?

Usage is implied by 'Current ... last price' and the note that it is free, but the description gives no explicit when-to-use or when-not-to-use guidance versus alternatives. An agent can infer this is for a quick price lookup, but alternatives are not acknowledged.

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