Skip to main content
Glama

Stratum Market Research

Search company rankings

search_rankings
Read-onlyIdempotent

Find data-defined top-10 company and country rankings by topic (for example "oncology trial sponsors", "medical device clearances").

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_rankings"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesTopic or keyword

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so safety is covered. The description adds one real behavioral trait — results are "data-defined" fixed "top-10" lists — but says nothing about what a result contains (IDs? editions? sponsors?) or how to follow up. It also leaves a mild tension unresolved between "top-10" and the schema's limit parameter that permits up to 25.

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?

A single front-loaded sentence with the resource and scope first and examples in parentheses; nothing is wasted. It is efficient but perhaps too spare given the unanswered questions about output and the limit parameter.

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

Completeness3/5

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

With no output schema and a search-style tool, the description should say what comes back and whether results link to the singular get_ranking sibling; neither is addressed. It is adequate to select the tool but not quite enough to use the result correctly.

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 50%: query is documented ("Topic or keyword") and the description's examples usefully clarify what a topic looks like, but limit (1-25, default 10) is never mentioned in either place and its relationship to the advertised "top-10" output is unexplained. With half the parameters undocumented, the description only partially compensates.

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 ("Find") and a specific resource ("top-10 company and country rankings") scoped "by topic", with two concrete query examples that make the resource tangible. It does not, however, differentiate itself from sibling get_ranking (singular, likely by ID) or search_reports, so an agent must infer the distinction.

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 only implied: the phrase "by topic" and the examples suggest this is the discovery/entry point when you have a keyword but no ranking identifier. There is no explicit when-to-use versus get_ranking or search_reports, and no stated next step (e.g., "then use get_ranking with the returned ID").

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