fsnb-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fsnb_rate_getB | Получить норму ГЭСН по коду (gesn:XX-XX-XXX-XX или голый код) |
| fsnb_searchA | Полнотекстовый поиск норм ГЭСН по наименованию и составу работ (FTS5) |
| fsnb_rate_composition | Состав ресурсов нормы: труд, машины, материалы (нормы расхода, не цены) |
| fsnb_validate_codeB | Проверить существование кода нормы в базе |
| fsnb_meta | Метаданные базы: редакция, источник, правовая основа, manifest, data_status |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: retrieve a specific norm by code, perform full-text search, and validate code existence. No overlap or ambiguity.
All tools use the 'fsnb_' prefix and underscore style, but the order of verb and object varies: 'rate_get' (object+verb), 'search' (verb-only), 'validate_code' (verb+object). Mostly consistent but not perfectly uniform.
3 tools is minimal but well-scoped for a norm lookup service: search, get by code, and validate. Not too many or too few for the intended functionality.
Covers essential read operations: retrieval, search, and existence check. Minor gaps like pagination or listing all codes are absent but not critical for the domain.