MY MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SAMPLE_SECRET | Yes | Your password here |
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 |
|---|---|
| get_fibonacci_sequenceB | Gets the Fibonacci sequence up to the nth number. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| summarize_text | Creates a prompt asking the LLM to summarize the provided text. |
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, as there are no other tools to compare it against. The tool's purpose is clearly defined and stands alone without ambiguity.
Since there is only one tool, naming consistency is inherently perfect; there are no other tool names to compare it with, so no inconsistencies can arise. The single tool name follows a clear verb_noun pattern.
A single tool is generally too few for most server purposes, as it limits functionality and scope, making the server feel thin and incomplete. For a server named 'MY MCP', which suggests a broader utility, one tool is insufficient to cover any meaningful domain.
With only one tool that generates a Fibonacci sequence, the server is severely incomplete for any inferred domain; it lacks basic operations like creation, update, or deletion, and offers no coverage beyond a single mathematical function, leading to dead ends for agents.