Skip to main content
Glama

Rank companies

rank_companies
Read-onlyIdempotent

Rank companies for a filing year by revenue, profit, employees, pay, margin or revenue change, optionally within a sector or municipality.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
sortNototalIncome
yearNoFiling year; defaults to the latest
limitNo
sectorNo
directionNodesc
municipalityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that results are scoped to a filing year and can be narrowed geographically or by sector, but says nothing about paging bounds (page max 20, limit max 50) or the return shape. With annotations doing the heavy lifting, this is adequate but not rich.

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 dense sentence that front-loads the verb and resource before the dimensions and optional filters. Nothing is wasted, though the list of metrics is packed in a way that takes a second read to map onto the enum values.

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?

Considering there is no output schema and only one schema-described parameter, the description covers the sort dimensions, the year scope and both optional filters. The notable omissions are pagination limits and sort direction meaning, which an agent could still infer from defaults in the schema.

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 only 14%, so the description must compensate. It does map colloquial terms to several enum values ('revenue' → totalIncome, 'pay' → averagePay, 'margin', 'revenue change'), which helps, but page, limit and direction (asc/desc, default desc) are left entirely to the schema.

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 ('Rank companies') plus the scope ('for a filing year') and the exact ranking dimensions. The verb 'rank' separates it from the search_* siblings by implication, though no sibling is named outright.

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?

The phrase 'optionally within a sector or municipality' implies the filtering use case, and 'for a filing year' implies the year scope. However, there is no explicit guidance on when to choose this over search_companies, nor any stated exclusions or prerequisites.

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