MCP Server Example
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 |
|---|---|
| addB | Adds two numbers a and b and returns 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 confusion or overlap between tools, making disambiguation perfect. The tool's purpose is clearly defined as adding two numbers, with no other tools to potentially conflict with.
With a single tool, naming consistency is inherently perfect as there are no other tools to compare against. The tool name 'add' follows a simple verb pattern, which is appropriate for its function.
A single tool for a server is generally too few for meaningful functionality, as it limits the server's scope and utility. While the tool is well-defined, the count feels thin and inadequate for most practical applications, indicating a mismatch in scope.
The server's domain appears to be basic arithmetic, but with only an addition tool, there are significant gaps in coverage (e.g., subtraction, multiplication, division). This incomplete surface will likely cause agent failures when other arithmetic operations are needed.