Skip to main content
Glama
ru-companies-mcp

ru-companies-mcp

company_financials

Retrieves annual revenue, net profit and assets from official Russian FNS financial statements using a company's INN to assess its financial health.

Instructions

Выручка, чистая прибыль и активы по годам из открытой отчётности ФНС (ГИР БО).

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": {
      "inn": "<inn>"
    },
    "name": "company_financials"
  }
}

Input Schema

NameRequiredDescriptionDefault
innYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does add real value by disclosing the source (open FNS/GIR BO), which implies coverage limits (only officially filed accounts; possibly no data for very new or small entities), but it says nothing about years covered, empty-result behavior, caching, or cost of the call.

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

Conciseness5/5

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

A single front-loaded sentence listing the returned metrics followed by the data source, with no filler or repetition. Nothing could be trimmed without losing information.

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?

An output schema exists, so return values need no explanation, and for a one-parameter lookup the description covers what data comes back and from where. The remaining gap is that it never states the input is an INN or how companies without filed statements behave.

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 description coverage is 0% and the description never mentions the sole parameter, so the connection to INN is only implied by the FNS context. The parameter name 'inn' is a well-known Russian company identifier, which keeps this workable, but the description adds no meaning beyond the schema itself.

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 a concrete resource set (revenue, net profit, assets by year) and its provenance (open FNS reporting / GIR BO), so the agent knows exactly what data this returns. It does not explicitly contrast itself with siblings like company_card or search_companies, but the financial-reporting scope is distinctive enough in practice.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no alternative tool is named. The agent must infer that this is the lookup to pick when financial figures are needed for an already-identified company, rather than e.g. company_card.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.