Sample Data MCP
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
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 |
|---|---|
| generate_test_data_toolC | Generate fixed-length test data based on a field specification |
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's purpose is clearly distinct as it is the sole tool available.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'generate_test_data_tool' follows a clear verb_noun pattern, but consistency cannot be assessed across multiple tools.
A single tool is generally too few for a server's purpose, as it limits functionality and suggests an incomplete or overly narrow scope. For a data generation server, one tool is insufficient to cover typical needs like varied data types or configurations.
The server's domain appears to be test data generation, but with only one tool, the surface is severely incomplete. It lacks operations for different data formats, validation, customization, or management, which are essential for comprehensive data handling.