utel-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_DEBUG | No | Set to "true" to log full request payloads to /tmp/mcp_debug.log | |
| HTTP_BEARER_TOKEN | No | Sets an Authorization: Bearer <token> header on every request | |
| HTTP_DEFAULT_HEADERS | No | JSON string of extra headers (e.g. {"X-Custom": "value"}). Invalid JSON is silently ignored. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_requestA | Send a request to the UTEL API. The |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_api_index | Index of all UTEL API documentation topics. |
| get_api_reference | Full comprehensive UTEL API reference — all endpoints, fields, types, and usage patterns. |
| get_skill | Full UTEL API skill document — comprehensive API reference for agents. Use this as context when working with UTEL API. |
TDQS
Scored across 1 tool
With only one tool, there is no potential for confusion between tools. The single tool has a distinct purpose: sending requests to the UTEL API.
Only one tool exists, so naming consistency is not an issue. The name 'send_request' follows a verb_noun pattern.
A single generic tool for an entire API surface is an extreme mismatch. The tool count is far too low for any non-trivial domain; it forces the agent to manage all API logic internally.
The single tool provides no specialized operations (e.g., CRUD, search), leaving agents to manually construct requests for every action. This is severely incomplete for a typical API interface.