Telos Model Context Protocol
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hello_toolD | Hello tool |
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
With only one tool, there is no possibility of ambiguity or overlap between tools, making disambiguation trivial and perfect.
The single tool name 'hello_tool' uses a consistent verb_noun pattern, and with only one tool, naming consistency is inherently perfect as there are no other names to compare against.
A single tool is too few for most practical server purposes, indicating a thin or trivial scope that may not support meaningful agent workflows, though it could be appropriate for a minimal demo or test server.
The server's purpose is unclear from the tool name and description, but a single 'hello_tool' suggests severe incompleteness, lacking any CRUD operations, lifecycle coverage, or domain-specific functionality that would enable agent tasks.