My UV MCP Server
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 |
|---|---|
| add_numbersA | Add two integers and return the result. |
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. The tool 'add_numbers' has a single, clearly defined purpose that cannot be confused with any other tool in this set.
The single tool name 'add_numbers' follows a clear verb_noun pattern, and with only one tool, there is no inconsistency to evaluate. The naming is straightforward and predictable in isolation.
A single tool is too few for most practical server purposes, as it severely limits functionality and scope. This feels thin and inadequate for handling any meaningful domain beyond a trivial operation, indicating a poor fit for typical MCP server use cases.
The server's purpose is unclear from the single tool, making it impossible to assess coverage meaningfully. With only a basic arithmetic operation, there are significant gaps in any plausible domain, rendering the tool surface severely incomplete for practical agent workflows.