Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
resolve_libraryA

Найти id библиотеки по названию сервиса (по-русски или по-английски): «юкасса», «тинькофф», «макс бот», «1с бсп». Пустой запрос - список всех библиотек.

get_docsB

Фрагменты документации по теме (topic - своими словами, можно по-русски: «вебхук возврата», «чек 54-ФЗ»). Первым блоком идут грабли - проверенные ловушки по теме. tokens - бюджет ответа.

get_gotchasB

Грабли по библиотеке: неочевидные ловушки интеграции (подписи, идемпотентность, копейки, тестовый режим, чеки). Без topic - все.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 3 tools

Disambiguation4/5

resolve_library is clearly distinct, while get_docs and get_gotchas overlap because get_docs already returns gotchas as its first block. The descriptions clarify the difference, but an agent may still hesitate when deciding whether to call get_docs or get_gotchas for trap information.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern: resolve_library, get_docs, get_gotchas. The only variation is resolve vs get, which is minor and still predictable.

Tool Count5/5

Three tools are well-scoped for a documentation lookup server: resolve a library, fetch documentation, and fetch gotchas. Each tool earns its place, and the count is neither thin nor excessive.

Completeness4/5

The core workflow of resolving a library and then retrieving docs or gotchas is covered. Minor gaps exist, such as no explicit topic listing, cross-library search, or version metadata, but agents can work around them.

Maintenance

ActivityMaintained
ResponsivenessNo issues