mcp-tool-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_TRANSPORT | No | Transport mode for the MCP server. Set to 'stdio' if a client will spawn this process directly instead of connecting over the network. | http |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_textA | Compute word, character, and sentence counts plus an estimated reading time. |
| fetch_url_metadataA | Fetch a URL and report its status code, content type/length, and response time. Does not raise on HTTP error status codes (4xx/5xx) -- those come back as data, since a 404 is a valid answer to "what does this URL return?". Only transport-level failures (timeout, DNS, connection refused, bad scheme) raise. |
| convert_temperatureA | Convert a temperature between celsius, fahrenheit, and kelvin. |
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 3 tools
Each tool operates on a completely different domain: text statistics, URL metadata, and temperature conversion. There is zero overlap, so an agent can easily distinguish between them.
All three tools follow a consistent verb_noun pattern (analyze_text, fetch_url_metadata, convert_temperature) using snake_case. The naming is uniform and predictable.
With exactly three tools, the set falls squarely within the typical well-scoped range (3-15). Each tool earns its place, providing a distinct and non-redundant utility.
Each tool individually covers its stated purpose comprehensively (text counts and reading time, HTTP metadata with non-error handling, and temperature conversion across all units). However, the overall server lacks a cohesive domain and could reasonably include additional common utilities, leaving a minor sense of incompleteness.