mcp-function-app-tester
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 |
|---|---|
| test_endpointC | Test a Function App endpoint and get detailed response information. The endpoint will be prepended to the base url which is: http://localhost:7071/api |
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 single tool has a clear, distinct purpose that cannot be confused with any other tool in this set.
The naming follows a consistent verb_noun pattern (test_endpoint). With only one tool, there is no inconsistency to evaluate, and the naming is clear and appropriate for its function.
A single tool is too few for a server named 'mcp-function-app-tester', which suggests broader testing capabilities. This minimal set feels thin and incomplete for the implied scope of testing Function App endpoints comprehensively.
The tool surface is severely incomplete for testing Function App endpoints. It only provides a basic test endpoint function, lacking essential operations like listing endpoints, managing test configurations, validating responses, or handling different HTTP methods and authentication scenarios.