Skip to main content
Glama
Sign In

tide

by ad.tide
OverviewDiscussionsAdmin

Coin prices

price
Read-onlyIdempotent

USD prices for up to 50 coins, now or at a past time. Pass coin types or symbols. Example: { coins: ["SUI", "DEEP"] }.

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": {
      "coins": "<coins>"
    },
    "name": "price"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNoOptional past time: ISO 8601 or unix seconds.
coinsYesCoin types or symbols, up to 50 (up to 10 symbols).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds useful context (USD denomination, 50-coin cap, historical support) but says nothing about price freshness, source, or what happens for unknown symbols.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the core capability, followed by the parameter hint and a runnable example. No wasted wording.

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 two-parameter, read-only tool with full schema coverage and no output schema, the definition is nearly sufficient. The gap is the return shape: with no output schema, the description does not say how prices map to the requested coins or how missing/unknown coins are represented.

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 it already documents both parameters, including the ISO 8601 / unix-seconds formats and the 50-item, 10-symbol limits. The description only adds a concrete example call, which is mildly helpful but not new semantics.

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?

"USD prices for up to 50 coins, now or at a past time" states a specific resource (coin prices), unit (USD), and scope (current or historical). It implicitly separates this from balance_at (balances), candles (OHLC series), and token_info (metadata), but never names those siblings.

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?

"now or at a past time" implies the two usage modes and the `at` parameter selects the historical one, but there is no explicit when-to-use vs. alternatives such as balance_at or candles, and no stated exclusions.

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

All tide 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