Skip to main content
Glama

Search StrictScore coins

search_coins
Read-onlyIdempotent

Finds StrictScore-covered crypto assets by name or ticker and returns each match with its slug, STRICT score, market data and page URL, largest market cap first. Call this first to get the slug the other tools need. Not for browsing by score or sector (use get_rankings). Example arguments: {"query": "eth", "limit": 5}.

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": {
      "query": "<query>"
    },
    "name": "search_coins"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum matches to return (1-20).
queryYesCoin name or ticker, for example "bitcoin" or "SOL". Partial names work.

Output Schema

NameRequiredDescriptionDefault
as_ofYesDate (YYYY-MM-DD) the result was served.
coinsYesMatches, largest market cap first.
caveatYesOne-line methodology caveat: research, not investment advice; scenarios are not forecasts.

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 declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is handled. The description adds real behavioral context beyond them: what fields come back and that results are ordered largest market cap first. It does not mention empty-result behavior or pagination, which keeps it short of 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 short sentences, front-loaded with purpose followed by sequencing, exclusion, and an example. Nothing is repeated from the schema verbatim and no sentence is filler.

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 two-parameter read-only search with full schema coverage, annotations, and an output schema, the description supplies everything needed to select and call it correctly. Return-value explanation is optional here since an output schema exists, and the brief field list is a bonus rather than a gap.

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%, so the baseline is 3; the description earns an extra point because "largest market cap first" explains which matches survive when limit truncates the set, which the schema does not convey. The example-arguments call adds a concrete invocation shape, though the schema already notes partial names work.

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?

Names a specific verb (Finds) and a precisely scoped resource (StrictScore-covered crypto assets) matched by name or ticker, and states what each result carries (slug, STRICT score, market data, page URL) plus ordering. An agent can distinguish it from list-oriented siblings such as get_rankings purely from this sentence.

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 explicit sequencing rule ("Call this first to get the slug the other tools need") and an explicit exclusion with the alternative named ("Not for browsing by score or sector (use get_rankings)"). Both when-to-use and when-not-to-use are covered.

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