Skip to main content
Glama

Digital Passport Belarus

Просмотр графа специализаций и отраслей

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

The annotations already declare readOnlyHint, idempotentHint, non-destructive behavior, and closed-world scope, so the description adds limited value by repeating that it works strictly in read-only mode. It does add useful context that the graph is two-level and includes confirmed-company counts, but it does not explain response format, pagination, or how counts are derived.

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?

The description is short and front-loads the core purpose. The final sentence about read-only mode is somewhat redundant because readOnlyHint is already set, but the overall structure remains efficient.

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?

For a simple read-only exploration tool with two optional, fully documented parameters and rich annotations, the description provides enough context to understand what is being explored. It could say more about the returned graph structure or how query and family affect results, but the core concept is adequately covered.

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 both query and family are already documented in the schema. The description does not add syntax, matching behavior, or examples beyond what the schema provides, making the baseline score appropriate.

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: viewing a two-level knowledge graph of Belarusian business, covering broad directions and canonical specializations with confirmed-company counts. This is clear enough to distinguish the tool from company-search or verification siblings, but it does not explicitly contrast itself with those alternatives.

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?

Usage is implied by the graph-exploration framing and by the schema fields for searching specializations and listing children of a direction. However, the description gives no explicit when-to-use guidance, no prerequisites, and no named alternatives for cases where company lookup or verification is more appropriate.

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.