Skip to main content
Glama

Ranking firm

rank_companies
Read-onlyIdempotent

Zwraca ranking firm według jednej miary: revenue (przychody), profit (zysk netto), growth (wzrost przychodów r/r), margin (marża netto), altman (wskaźnik Altmana Z) albo valuation (wycena AI), z wartością miary, opcjonalnie dla jednego miasta. Użyj do pytań „największe, najbardziej zyskowne, najszybciej rosnące firmy”; nie użyj do porównania dwóch konkretnych firm (wołaj dla nich get_company z sekcją financials). Koszt w trybie Pro: 0 operacji. Ranking obejmuje tylko firmy ze zbadanymi sprawozdaniami. Przykład: {"metric": "revenue", "city": "Gdańsk", "limit": 10}.

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

Input Schema

NameRequiredDescriptionDefault
cityNoMiasto z listy serwisu, np. "Gdańsk"; bez niego ranking krajowy.
limitNoIle firm (domyślnie 20, najwyżej 100).
metricYesMiara rankingu: revenue (przychody), profit (zysk netto), growth (wzrost r/r), margin (marża netto), altman (wskaźnik Altmana Z), valuation (wycena AI).

Output Schema

NameRequiredDescriptionDefault
modeYes
itemsYes
sourceNo
next_pageYes
total_countNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare readOnly and idempotent; the description adds real behavioural context: zero operation cost on the Pro plan, the coverage caveat that the ranking includes only companies with examined/audited financial statements, and a concrete call example. The one missing trait is sort order (implicitly descending from 'largest' but never stated).

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?

Single dense paragraph that front-loads the resource, then metrics, then usage routing, then caveats and example — good ordering. It does repeat the full metric list already present in the enum descriptions, which is redundant but keeps the tool 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 annotations, a full schema and an output schema present, the description supplies the remaining decision-relevant facts: cost, data-coverage limitation, alternative route and an example payload. Only sorting direction and the meaning of the AI 'valuation' score remain unstated.

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 each parameter already carries its own description and enum glosses, so the description's metric glosses mostly restate the schema. The only added value is the worked example showing metric+city+limit combined; baseline 3 applies when the schema does the heavy lifting.

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?

Names a specific verb+resource (returns a company ranking) and enumerates exactly which measures can be ranked (revenue, profit, growth, margin, altman, valuation), plus the optional city scoping. It also explicitly contrasts itself with get_company, so an agent can distinguish it from siblings without opening any 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?

States the triggering question types ('largest, most profitable, fastest growing companies') and an explicit exclusion: do not use it to compare two specific companies, call get_company with the financials section instead. When-to-use, when-not-to-use and the named alternative are all present.

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