Libs MCP Service
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MODE | No | UI mode: light (minimal) or standard (full). Affects tool list and response shape | standard |
| API_TOKEN | Yes | Authentication token for the external platform | |
| API_BASE_URL | Yes | Base URL for the external API |
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 |
|---|---|
| listC | List entities (supports UA/RU/EN resource names) |
| getC | Get single entity by ID (short form in light mode) |
| createA | Create an entity for the given resource. Payload shape depends on resource (e.g., departments, professions, languages, etc.). For entities with terms, provide mainTerm and optional terms with correct IDs/types. IMPORTANT: When creating AI-generated content, ALWAYS include aiMetadata fields with ai_generated=true, ai_model (e.g., "gpt-4o-mini"), and ai_generation_date. Only attach aiMetadata to the specific term(s) you are creating; terms without aiMetadata will not be touched. |
| updateA | Update an entity by ID for the given resource. Payload shape depends on resource. For term-managed entities, send the FULL terms array on update to avoid deletions (include unchanged terms with their IDs). IMPORTANT: Include aiMetadata ONLY for the term(s) you want to update; other terms without aiMetadata in the payload will keep their existing AI metadata. Recommended fields when updating AI-generated content: ai_generated=true, ai_model (e.g., "gpt-4o-mini"), ai_generation_date. |
| get_term_typesC | Get all term types |
| get_prioritiesC | Get all priorities |
| get_priorityA | Get single priority by ID |
| find_existing_responsibility_termsA | Find existing Actions and Objects by language to check what terms already exist. Use this BEFORE adding new terms to responsibilities. This tool helps you find existing responsibility combinations or check if a specific action-object pair already has terms. |
| find_existing_skill_termsA | Find existing Skills by responsibility and tool to check what terms already exist. Use this BEFORE adding new terms to skills. This tool helps you find existing skill combinations or check if a specific responsibility-tool pair already has terms. |
| create_termA | Create a new individual term using API token authentication. Terms can exist independently and be linked to term groups. IMPORTANT: When creating AI-generated terms, ALWAYS include aiMetadata with ai_generated=true, ai_model (e.g., "gpt-4o-mini"), and ai_generation_date for proper tracking. Only the created term’s AI metadata is affected. |
| update_termA | Update an existing individual term using API token authentication. IMPORTANT: Send aiMetadata only when you intend to change AI fields for this term; omitting aiMetadata leaves existing AI fields unchanged. Recommended: include ai_generated=true, ai_model, ai_generation_date. Supports version tracking and term group relation management. |
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 11 tools
Generic tools like list/get/create/update overlap with specialized tools like get_priority, create_term, and update_term, making it unclear whether to use the generic path or the specialized one for term and priority operations. Descriptions help clarify intent, but the boundaries are not crisp.
The generic operations use bare verbs (list, get, create, update) while the specialized operations use verb_noun patterns (get_priority, create_term, find_existing_skill_terms), so the naming convention is mixed. All names are readable and consistently snake_case, but the pattern is not uniform.
Eleven tools is a reasonable count for an entity/term management server, covering generic resource operations plus dedicated priority, term type, and lookup helpers. Each tool appears purposeful and the set is not bloated.
The tool surface covers list, get, create, and update operations, but there is no delete operation for entities or terms, which leaves the lifecycle incomplete. The find_existing_* helpers partially cover term discovery, but dedicated term listing/retrieval is still somewhat implicit.