Skip to main content
Glama

Get StrictScore rankings

get_rankings
Read-onlyIdempotent

Lists assets ranked by STRICT score (default), market cap, price, 24h change, volume, upside or name, optionally filtered by sector and score range, one page at a time. Use it to find the strongest or weakest assets in a sector. Not for looking up one named coin (use search_coins) or for a full analysis (use get_coin_analysis). Example arguments: {"sector": "Layer 2", "minScore": 60, "sortBy": "strictScore", "limit": 10}.

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": "get_rankings"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1.
limitNoRows per page (1-50).
sectorNoSector name exactly as returned by list_sectors. Omit for all sectors.
sortByNoField to sort by.strictScore
maxScoreNoOnly assets with a STRICT score of at most this value (0-100).
minScoreNoOnly assets with a STRICT score of at least this value (0-100).
sortOrderNoSort direction.desc

Output Schema

NameRequiredDescriptionDefault
as_ofYesDate (YYYY-MM-DD) the result was served.
coinsYes
caveatYesOne-line methodology caveat: research, not investment advice; scenarios are not forecasts.
paginationYes
source_urlYesCanonical strictscore.com page to cite.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/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 safety is covered. The description adds behavior the annotations do not: results are paginated ('one page at a time') and strictScore is the default ranking. It stops short of describing result ordering semantics or total-count behavior, which keeps it at 4 rather than 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?

The ranked-list scope is front-loaded in the first clause, the routing guidance follows, and the example comes last as optional illustration. Every sentence carries distinct information: capabilities, anti-use-cases, and a valid call sample.

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?

With an output schema present and 100% parameter coverage, the description only needs to establish purpose, routing, and pagination behavior, all of which it does. An agent has enough to select this over siblings and to construct a valid filtered, sorted, paged call.

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 description coverage is 100%, so every parameter (page, limit, sector, sortBy, minScore, maxScore, sortOrder) is already documented with bounds, defaults, and enums. The description reinforces the default sort and supplies a concrete argument example, but adds no constraints or semantics beyond what the schema states. 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?

Opens with a specific verb and resource ('Lists assets ranked by...') and enumerates the exact sort fields, including which is the default. It also scopes the resource with 'optionally filtered by sector and score range, one page at a time', so an agent knows the shape of the output without opening the 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?

Explicitly names the use case ('find the strongest or weakest assets in a sector') and then rules out two alternatives by name: search_coins for a single named coin and get_coin_analysis for full analysis. Both a when and a when-not are stated with the replacement tool identified.

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