Skip to main content
Glama

Digital Passport Belarus

explore_knowledge_graph

Просмотр двухуровневого графа знаний белорусского бизнеса: широких направлений и канонических специализаций с количеством подтверждённых компаний. Работает строго в режиме чтения.

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

Input Schema

NameRequiredDescriptionDefault
queryNoПоисковый запрос по названию специализации
familyNoСлаг широкого направления для получения дочерних специализаций

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?

No annotations are supplied, so the description carries the full burden; it does usefully disclose that the tool works strictly read-only and that results include counts of confirmed companies. It omits other behaviorally relevant facts: whether the graph is a static snapshot or live, whether there are rate limits or auth requirements, and how large the returned tree can get.

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?

Two dense sentences with no filler. The resource and its two-level structure are front-loaded, and the read-only constraint is a short, useful second sentence rather than padding.

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 two optional parameters and no output schema, so the description should cover the zero-argument case and the shape of the returned tree; it does neither. It is adequate for understanding what the tool is, but leaves an agent guessing about default and combined-parameter behavior.

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%, so both parameters are already documented and the baseline is 3. The description adds context by framing the two levels (broad directions vs canonical specializations), which loosely maps to the family and query parameters, but it does not say what happens when both are supplied, when neither is supplied, or how matching is performed.

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 and resource (viewing a two-level knowledge graph of Belarusian business) and clarifies the two levels it exposes (broad directions and canonical specializations with counts of confirmed companies). That is far more specific than the siblings (search_belarus_companies, get_company_passport, verify_belarus_unp), which are company-level lookups, but it never explicitly states the contrast.

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?

Use is only implied: browsing a taxonomy of directions and specializations. The description gives no explicit 'use this when…' rule, no mention of when to prefer this navigation tool over search_belarus_companies, and no explanation of how the two access modes relate to each other.

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