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
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_listingsC

Search the GET4AGENT MARKET catalog of KYA-verified API listings.

get_listingA

Get full detail (price, seller KYA status, seller DID) for one listing.

verify_agentC

Check an agent's KYA / identity status.

track_parcelA

Track a Kazakhstan Post (Kazpost) parcel by barcode — status + route history.

validate_iinA

Validate a Kazakhstan IIN / BIN (checksum) and parse it.

validate_kz_ibanB

Validate a Kazakhstan IBAN (ISO 7064 mod-97).

lei_lookupB

Look up a global Legal Entity Identifier (GLEIF) by LEI or name.

kzt_ratesC

Current KZT (Kazakhstani tenge) exchange rates.

fx_ratesC

ECB reference FX cross-rates (Frankfurter).

weatherA

Current weather + short forecast for a latitude/longitude (Open-Meteo).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 10 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: search vs. detail, identity verification, parcel tracking, validation of various identifiers, rate lookups, and weather. No two tools overlap in functionality, making selection unambiguous.

Naming Consistency4/5

Tool names are all lowercase snake_case and mostly follow a verb_noun pattern (search_listings, get_listing, verify_agent, track_parcel, validate_iin, validate_kz_iban, lei_lookup). A few are noun-only (kzt_rates, fx_rates, weather), but these are still predictable and consistent in style.

Tool Count5/5

With 10 tools, the server sits comfortably in the ideal range. The number is manageable and each tool has a defined role, even if some are tangential to the marketplace theme.

Completeness2/5

The marketplace surface is incomplete: it only supports searching and viewing listings, missing create, update, delete, or purchase operations. The remaining utilities (track_parcel, validate_iin, weather, etc.) form an incoherent mix with no clear workflow connecting them to the marketplace, leaving significant dead ends.

Maintenance

ActivityMaintained
ResponsivenessNo issues