Skip to main content
Glama

Поиск белорусских компаний в реестре

search_belarus_companies
Read-onlyIdempotent

Поиск белорусских организаций по названию, бренду, УНП, городу или специализации из графа знаний. Работает строго в режиме чтения.

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

Input Schema

NameRequiredDescriptionDefault
cityNoГород или слаг города для фильтрации
queryNoНазвание организации, бренд, услуга или 9 цифр УНП
categoryNoСлаг отраслевой рубрики
has_siteNoТолько организации с подтверждённым официальным сайтом
verifiedNoТолько организации со статусом «Верифицировано»
min_yearsNoМинимальный возраст компании на рынке в годах (5 или 10)
specializationNoСлаг или название специализации из графа знаний

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, and the sentence 'Работает строго в режиме чтения' merely restates readOnlyHint. Nothing is added about result limits, pagination, coverage of the registry, or what happens when all filters are omitted (all parameters are optional).

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?

Two short sentences with the searchable fields front-loaded; no wasted clauses. The second sentence is largely redundant with the readOnlyHint annotation, which keeps it from a 5.

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?

The tool has 7 optional parameters and no output schema, and annotations cover the safety profile, but the description never explains default behavior with zero filters, expected result shape, or how results are ranked. Adequate but with clear gaps for a broad search tool.

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 100%, so the baseline is 3; every parameter is documented in the schema, including the 9-digit УНП format and the 5/10 enum for min_years. The description echoes the searchable fields but adds no syntax, matching behavior, or combination rules beyond what the schema already provides.

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 states a specific verb ('Поиск') and resource ('белорусских организаций') plus the searchable fields (название, бренд, УНП, город, специализация) and the data source (граф знаний). It does not distinguish the tool from siblings such as verify_belarus_unp or get_company_passport, so it stops short of a 5.

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 named alternative. An agent must infer from sibling names alone whether to search here first or to call verify_belarus_unp or get_company_passport for a specific company.

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.