Skip to main content
Glama

list_rankings

Read-only

Compare ratings or distinct sources reporting use in the last 30 days. Filter by task tag or runtime.

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": {
      "metric": "<metric>"
    },
    "name": "list_rankings"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNo
limitNoResults per page. Default: 5.
cursorNoPass the previous next_cursor back unchanged.
metricYes
runtimeNo
versionNo
deliveryNo
initiationNo
evaluation_basisNo

Output Schema

NameRequiredDescriptionDefault
basisYes
itemsYes
metricYes
statusYes
next_cursorYes
window_daysNo
minimum_rating_sourcesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare read-only, non-destructive, open-world behavior, so the description does not need to restate safety. It adds useful context by specifying the 30-day evaluation window and that the metric selects ratings versus reported usage, but it omits pagination behavior despite the limit and cursor parameters.

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

Conciseness4/5

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

The description is two tight sentences with the core comparison and filters front-loaded, and there is no wasted wording. However, its brevity contributes to under-specification because the second sentence covers only two of the available filters.

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

Completeness2/5

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

For a 9-parameter tool with low schema description coverage, the description is too sparse: it does not explain four filter enums or pagination behavior. Since an output schema exists, return values need not be detailed, but the invocation surface remains incomplete.

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

Parameters2/5

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

Schema description coverage is only 22%, so the description must compensate for undocumented parameters. It gives meaning to metric, tag, and runtime, but leaves version, delivery, initiation, and evaluation_basis entirely unexplained even though these appear to be important filters.

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?

The description names the operation as comparing ratings or distinct sources reporting use, scoped to the last 30 days, and identifies task tag and runtime as filters. It is specific enough to distinguish a rankings comparison from raw usage reports, though it does not explicitly name a sibling alternative.

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?

It implies this tool is for rankings/usage comparisons over the last 30 days with optional tag and runtime filters. However, it does not state when to prefer it over list_usage_reports or other siblings, nor does it provide exclusions or prerequisite conditions.

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