DotnetFastMCP
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_numbersB | Adds two integers and returns their sum |
| TestContextC | Processes input with progress reporting via McpContext |
| greet_userA | Returns a personalised greeting for the given user name |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze_code | Analyzes a code snippet for potential improvements, bugs, or style issues. |
| generate_test | Generates unit test code for a specified function and requirements. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| config | Application configuration settings |
TDQS
Scored across 3 tools
Each tool has a distinct purpose: add_numbers does addition, greet_user does greetings, and TestContext handles context-based processing. Only TestContext has a somewhat vague name, but its description makes it distinguishable.
Naming is inconsistent: add_numbers and greet_user use snake_case, while TestContext uses PascalCase and lacks a verb. The mix of conventions reduces predictability.
With only 3 tools, the server appears under-scoped for a general-purpose MCP server. This is too few to cover common operations, making the set feel thin.
The tools are trivial and unrelated, with no clear domain or CRUD operations. There is no meaningful coverage of any real-world use case, leaving significant gaps.