mcp-avangenio-services
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| avangenio_get_statusA | Gets the current status of Avangenio's services (Internet, bandwidth per user, battery level, and state electrical service), read from https://status.avangenio.com/data.txt. Returns JSON with normalized values (booleans and numbers) plus a 'raw' object with the original pairs. Takes no arguments. |
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 1 tool
Only one tool exists, so there is no possibility of confusing it with another tool. The single tool has a clear, specific purpose.
The tool name follows a clear verb_noun pattern ('avangenio_get_status'), but with only one tool there is no broader pattern to evaluate. Still, the name is descriptive and consistent with common MCP conventions.
A single tool is minimal but fully appropriate for the narrow scope of retrieving service status. It feels slightly thin compared to richer servers, but the count matches the stated purpose without being wasteful.
The tool covers all aspects of the described purpose: internet status, bandwidth, battery, and electrical state. Returns both normalized and raw values, so no obvious gaps in the domain.