MCP Server Demo
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 |
|---|---|
| sum_two_numbersC | Add two numbers |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| read_build_ci_file | Read the Java build CI job template. This template contains .build-java job that can be extended for Maven-based Java applications. Use this template when creating GitLab CI files for Java projects that need build functionality. |
| read_sast_scanner_ci_file | Read the SAST scanner CI job template. This template contains .sast-scan-java job for Static Application Security Testing of Java applications. Use this template when creating GitLab CI files that need security scanning capabilities. |
| read_sca_scanner_ci_file | Read the SCA scanner CI job template. This template contains .scan-scan-java job for Software Composition Analysis of Java applications. Use this template when creating GitLab CI files that need dependency vulnerability scanning. |
| read_build_image_ci_file | Read the Docker build image CI job template. This template contains build-image job for building and pushing Docker images to registry. Use this template when creating GitLab CI files that need containerization capabilities. |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools, making it trivially distinct.
The single tool name 'sum_two_numbers' follows a clear verb_noun pattern, and with only one tool, consistency is inherently perfect.
A single tool is generally too few for a server's purpose unless it's extremely narrow; this feels thin and may not cover a meaningful domain adequately.
The tool surface is severely incomplete, as a single addition tool does not provide any meaningful coverage or lifecycle for a domain, leaving obvious gaps for any practical use.