Skip to main content
Glama
hyen43

Model Context Protocol Server

by hyen43

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
example_toolC

An example tool that processes messages

weather_apiC

Open-Meteo API를 사용하여 도시의 실제 날씨 정보를 가져오기

weatherC

도시의 날씨 정보를 가져오기

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

C2.6/5.0

Scored across 3 tools

Disambiguation2/5

The 'weather' and 'weather_api' tools have significant overlap in purpose, as both appear to fetch weather information for a city, making them ambiguous and prone to misselection. The 'example_tool' is distinct but vague, adding to the overall confusion in the tool set.

Naming Consistency3/5

The naming is mixed with 'example_tool' and 'weather_api' using snake_case, while 'weather' is a single word, showing some inconsistency. However, the names are still readable and follow a basic pattern, but lack a uniform verb_noun structure or consistent style.

Tool Count3/5

With only 3 tools, the count is borderline thin for a general-purpose server like 'Model Context Protocol Server', suggesting it might be under-scoped. While not extreme, it feels insufficient to cover a broad domain effectively, indicating a potential mismatch in scope.

Completeness2/5

The tool set is severely incomplete for the server's implied domain, with overlapping weather tools and a vague example tool, leaving obvious gaps in functionality. There is no clear coverage of core operations or a coherent workflow, which will likely cause agent failures due to missing essential capabilities.

Maintenance

ActivityInactive
ResponsivenessNo issues