Skip to main content
Glama
Sign In

Statsnet

by io.github.usenetstate
OverviewDiscussionsAdmin

get_company

Публичная карточка компании в Markdown: статус, регистрация, руководство, показатели (госконтракты, суды), финансы.

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": {
      "jurisdiction": "<jurisdiction>",
      "identifier": "<identifier>"
    },
    "name": "get_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
identifierYesБИН/ИИН компании
jurisdictionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / jurisdiction / enum
      Previous value: -[
-  "kz",
-  "uz",
-  "kg",
-  "ge",
-  "am",
-  "tj",
-  "az"
-]New value: +[
+  "kz",
+  "uz",
+  "kg",
+  "ge",
+  "am",
+  "tj",
+  "az",
+  "us-ak",
+  "us-al",
+  "us-ar",
+  "us-az",
+  "us-ca",
+  "us-co",
+  "us-ct",
+  "us-dc",
+  "us-de",
+  "us-fl",
+  "us-ga",
+  "us-hi",
+  "us-ia",
+  "us-id",
+  "us-il",
+  "us-in",
+  "us-ks",
+  "us-ky",
+  "us-la",
+  "us-ma",
+  "us-md",
+  "us-me",
+  "us-mi",
+  "us-mn",
+  "us-mo",
+  "us-ms",
+  "us-mt",
+  "us-nc",
+  "us-nd",
+  "us-ne",
+  "us-nh",
+  "us-nj",
+  "us-nm",
+  "us-nv",
+  "us-ny",
+  "us-oh",
+  "us-ok",
+  "us-or",
+  "us-pa",
+  "us-pr",
+  "us-ri",
+  "us-sc",
+  "us-sd",
+  "us-tn",
+  "us-tx",
+  "us-ut",
+  "us-va",
+  "us-vt",
+  "us-wa",
+  "us-wi",
+  "us-wv",
+  "us-wy"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / jurisdiction / enum
      Previous value: -[
-  "kz",
-  "uz",
-  "kg",
-  "ge",
-  "am"
-]New value: +[
+  "kz",
+  "uz",
+  "kg",
+  "ge",
+  "am",
+  "tj",
+  "az"
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / jurisdiction / enum
      Previous value: -[
-  "kz",
-  "uz",
-  "kg"
-]New value: +[
+  "kz",
+  "uz",
+  "kg",
+  "ge",
+  "am"
+]
  4. First observed

TDQS

B3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose useful behavior: the output format (Markdown) and the categories of data returned. However, it says nothing about whether the lookup is read-only, authorization requirements, or what happens when the identifier is not found.

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 well-formed sentence with the resource and its payload front-loaded; nothing is wasted. It is arguably too terse for the parameter complexity involved, but structurally sound.

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, the description does explain what is returned, which is the main burden. It still omits required context for a multi-jurisdiction lookup: identifier format per jurisdiction, failure behavior, and how it relates to search_companies.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 50%: 'identifier' is documented as БИН/ИИН but 'jurisdiction' is a bare enum of ~58 country/state codes with no description. The description adds no parameter meaning at all, leaving the agent to guess which jurisdictions are supported and how identifiers differ per jurisdiction.

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 specific verb-implied resource (public company card) and enumerates the content sections it returns (status, registration, management, indicators, finances). It is clearly the single-entity lookup counterpart to search_companies, though it never names that sibling to draw the contrast explicitly.

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 statement of when to use this tool versus search_companies, nor any prerequisite (e.g. 'use this once you have an exact BIN/IIN; use search_companies to find one'). The distinction from the sibling must be inferred entirely from the word 'card'.

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

All Statsnet toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources