RPG-Schema MCP server
Server Details
MCP server for the RPG-Schema.org definition and helping the usage of RPG-Schemas in TTRPG manuals
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 3.6/5 across 6 of 6 tools scored.
Each tool has a clearly distinct purpose with no overlap: add_ontology registers new ontologies, compose merges them, inspect_ontology examines one, list_ontologies catalogs them, search_classes finds classes, and search_properties finds properties. The separation between search_classes and search_properties is particularly well-defined.
All tools follow a consistent verb_noun pattern with snake_case: add_ontology, compose, inspect_ontology, list_ontologies, search_classes, and search_properties. The naming is predictable and readable throughout the set.
With 6 tools, this server is well-scoped for managing ontologies in an RPG context. Each tool earns its place by covering distinct operations like registration, composition, inspection, listing, and searching, without being overly sparse or bloated.
The tool set provides strong coverage for ontology management, including CRUD-like operations (add, list, inspect) and composition/search functions. A minor gap exists in lacking update or delete tools for ontologies, but agents can likely work around this by re-adding or ignoring modifications.
Available Tools
6 toolsadd_ontologyInspect
Register a new baseline ontology by providing its TTL content. The ontology is saved to the catalog and becomes available for inspection, search, and composition.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | ||
| tags | No | ||
| label | No | ||
| description | No | ||
| ttl_content | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
composeInspect
Compose multiple baseline ontologies into a single schema card. Pass a list of ontology slugs. Returns a merged schema card ready to use as the starting point for extraction.
| Name | Required | Description | Default |
|---|---|---|---|
| slugs | Yes | ||
| target_namespace | No |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
inspect_ontologyInspect
Inspect a baseline ontology: returns all classes, datatype properties, and object properties in schema-card format.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
list_ontologiesInspect
List all registered baseline ontologies in the catalog.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
search_classesInspect
Search for classes across all registered ontologies. Matches class name or description (case-insensitive substring).
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
search_propertiesInspect
Search for properties (datatype + object) across all ontologies. Matches property name, domain, range, or description.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!