Skip to main content
Glama

Supported coins and tickers

list_supported_coins
Read-onlyIdempotent

Find valid filters before a coin request: returns tracked market coins with symbol and rank, plus recent news ticker counts. News tickers may be stocks or forex. Free, no account or API key.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_supported_coins"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context beyond them: the tool is free with no account or API key, and news tickers may be stocks or forex — a data-mixing caveat an agent could not get from structured fields.

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 action and its trigger, then the payload, then the ticker caveat and access terms. No sentence is padding; each adds a fact an agent needs.

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?

With no output schema, the description carries the burden of describing return values and does so at a summary level (symbol, rank, news ticker counts). It stops short of describing response shape or ordering, but for a zero-argument discovery endpoint this is close to sufficient.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter meaning to explain; the baseline for 0 params applies. The description appropriately spends its space on return content instead of inventing argument detail.

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 a concrete purpose (discover valid filter values before a coin request) and names the returned contents: tracked market coins with symbol and rank plus recent news ticker counts. It is clear what the tool does, though it never names or contrasts with the closest sibling, market_catalogue, so an agent must infer the boundary from names alone.

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?

'Find valid filters before a coin request' gives a clear usage condition and ordering cue. It does not state when NOT to use it or which sibling to prefer for catalogue-style lookups, so the guidance is contextual but not exclusive.

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