Skip to main content
Glama

Stratum Market Research

Get a ranking

get_ranking
Read-onlyIdempotent

Get one ranking as Markdown: rank, company or country, its value, the measure and the period. Accepts a ranking slug, page URL or title.

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": {
      "ranking": "<ranking>"
    },
    "name": "get_ranking"
  }
}

Input Schema

NameRequiredDescriptionDefault
rankingYesRanking slug, page URL or title

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.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, closed-world behavior, so the safety profile is covered. The description adds real value on top by disclosing the return format (Markdown) and the shape of the returned row.

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?

Two short sentences, front-loaded with the output format and followed by the identifier forms. The second sentence duplicates the schema description verbatim, which is minor waste but keeps the definition self-contained.

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 usefully explains what the Markdown payload contains, and it covers all accepted identifier forms for the only parameter. It does not state what happens when the identifier fails to resolve, a modest gap for a lookup tool.

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 coverage is 100% and the single parameter is documented as "Ranking slug, page URL or title". The description restates exactly that phrasing, adding no resolution rules, precedence, or error behavior beyond the schema. Baseline 3 applies.

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 specific verb and resource ("Get one ranking") and enumerates the returned fields (rank, company/country, value, measure, period). The singular "one ranking" implicitly contrasts with the multi-result search_rankings sibling, though it never names it.

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?

Usage is implied: fetch a single ranking when you already have an identifier for it, versus searching. No explicit when-not guidance or named alternative, so the agent must infer that search_rankings is the discovery path.

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