Skip to main content
Glama
agh-skos-mcp

agh-skos-mcp

by kbzowski

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
list_filter_optionsA

List allowed values for a dictionary filter of search_people.

field: one of tytul, id_status, grupa, stanowisko, funkcja, jednostka, pawilon, cialo. contains: optional case-insensitive substring to narrow the list.

search_peopleA

Search AGH staff in the SkOs directory (skos.agh.edu.pl advanced search).

Text filters (nazwisko, imie, email, pokoj, telefon) are case-insensitive prefix matches - no wildcards. Dictionary filters (tytul, id_status, grupa, stanowisko, funkcja, jednostka, pawilon, cialo) accept either the numeric id or the Polish label - use list_filter_options to browse them.

Returns matching people with their title, unit and profile url; pass that url to get_person for contact data. When exactly one person matches, the full profile is already included in the "person" field.

get_personA

Fetch a full SkOs profile: units, position, room, phones, email, www.

person: profile url or slug as returned by search_people, e.g. "/osoba/krzysztof-bzowski-7674.html" or "krzysztof-bzowski-7674".

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly separate role: list_filter_options is a helper for enumerating dictionary values, search_people queries the directory, and get_person retrieves a single full profile. The descriptions even explain the intended workflow (use filter options before searching, pass the returned url to get_person), so an agent cannot easily confuse them.

Naming Consistency5/5

All three names follow a strict verb_noun snake_case pattern (list_filter_options, search_people, get_person) with verbs that match the action performed. No mixed casing or inconsistent verb styles.

Tool Count5/5

Three tools is a tight, purpose-built surface for a read-only directory lookup service: browse vocabularies, search, then fetch details. No redundant or filler tools, and nothing appears artificially split.

Completeness4/5

The read-only lifecycle (browse filters -> search -> full profile) is fully covered, and the single-match shortcut in search_people avoids a dead end. Minor gaps remain, such as no pagination or batch/export option for large result sets, but agents can work around these by narrowing search filters.

Maintenance

ActivityNo data
ResponsivenessOutdated data