rce-cho-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 |
|---|---|
| pingA | Test of de MCP-server bereikbaar is. |
| query_sparqlB | Voer een SPARQL SELECT of ASK query uit op het RCE CHO endpoint. |
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 2 tools
ping and query_sparql serve completely different purposes: connectivity test vs data query. No overlap.
Both names are clear, but 'ping' is a simple verb while 'query_sparql' follows verb_noun. Minor inconsistency but acceptable for a small set.
With only 2 tools, the surface is thin but not unreasonable for a focused SPARQL endpoint server.
Missing essential tools like schema listing, prefix resolution, or data manipulation, leaving significant gaps for real-world use.