Skip to main content
Glama
Sign In

SimianX AI

by io.github.SimianX-AI
OverviewDiscussionsAdmin

Get crypto quotes

get_crypto_quotes
Read-onlyIdempotent

Latest prices of the coins on the Market Pulse board (the large caps and the coins users filter on), up to 120 per call; coins it does not carry come back in missing (get_crypto_candles has any pair). Nothing found, nothing charged. (0.1 points 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": {
      "symbols": "<symbols>"
    },
    "name": "get_crypto_quotes"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolsYesComma-separated coins, e.g. BTC,ETH,SOL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the description only needs to add what annotations cannot. It does: a hard cap of 120 per call, partial-result semantics via the `missing` key, and billing behavior ('nothing found, nothing charged', 0.1 points per call) — unusually rich operational context. It does not describe what constitutes a returned quote.

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?

Purpose is front-loaded and every clause carries information: scope, cap, missing-key behavior, alternative, billing. The stacked parentheticals make it dense, but no sentence is filler.

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

Completeness4/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 output schema, the description covers cost, limits, and failure/partial-result behavior. The one remaining gap is that the shape of a returned quote (fields like price, change) is never described and no output schema exists to compensate.

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 coverage is 100% and the single `symbols` parameter already documents comma-separated format with an example (BTC,ETH,SOL). The description adds nothing about the parameter itself, so the baseline 3 applies.

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?

States a specific verb and resource ('Latest prices of the coins') plus the precise coverage scope ('on the Market Pulse board — the large caps and the coins users filter on'), and explicitly distinguishes itself from get_crypto_candles for arbitrary pairs. An agent can route between the two without opening either 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?

Clear context for when this tool applies (latest snapshot of board-covered coins) and names the alternative for coins outside that set. It stops short of an explicit 'do not use for historical data / time series' exclusion, but the sibling pointer covers the main branching decision.

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

All SimianX AI toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources