Skip to main content
Glama

Compare StrictScore coins

compare_coins
Read-onlyIdempotent

Returns the full StrictScore analyses of up to 5 assets in one call, in request order, with null for a slug that has no analysis (if none of the slugs has one, an error naming them). Use it to compare assets side by side. Not for a single asset (use get_coin_analysis) or for finding slugs (use search_coins). Example arguments: {"slugs": ["bitcoin", "ethereum", "solana"]}.

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": {
      "slugs": "<slugs>"
    },
    "name": "compare_coins"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugsYes1 to 5 slugs. StrictScore slug as returned by search_coins, for example "bitcoin" or "ethereum".
localeNoLanguage of the written analysis (overview, thesis, risks). Scores and numbers do not change.en

Output Schema

NameRequiredDescriptionDefault
as_ofYesDate (YYYY-MM-DD) the result was served.
caveatYesOne-line methodology caveat: research, not investment advice; scenarios are not forecasts.
resultsYesOne entry per distinct slug, in request order.
not_foundYesSlugs with no analysis; use search_coins.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, non-destructive, closed-world), so the bar is lower, but the description still adds real behavioral detail beyond them: per-slug null padding for missing analyses, and a total-miss error that names the slugs. A concrete example-argument JSON also shows calling shape. It stops short of describing response size or latency characteristics, so not a 5.

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 compact sentences plus a single example, with the core contract front-loaded and the routing exclusions immediately after. Nothing is redundant with the title or with structured fields.

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

Completeness5/5

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

For a 2-parameter read tool with a full output schema, all an agent needs is present: batching limits, ordering, partial-failure behavior, and sibling routing. Return-value structure is correctly left to the output schema rather than duplicated.

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?

Schema coverage is 100% and the slugs parameter is already self-documenting, so the baseline is 3. The description earns one more point by pinning down that results come back "in request order" — array-position semantics the schema does not state — and by giving a worked example of the slugs array.

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 ("Returns the full StrictScore analyses"), the batch cap ("up to 5 assets in one call"), and the ordering contract ("in request order"). It explicitly names the two siblings it is not (get_coin_analysis, search_coins), so an agent can distinguish it without opening any schema.

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

Usage Guidelines5/5

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

Gives an affirmative use case ("compare assets side by side") plus explicit exclusions with the correct alternative for each: single asset goes to get_coin_analysis, slug discovery goes to search_coins. Routing is fully determined.

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