Skip to main content
Glama
joseabantomarin

wquestions-mcp

by joseabantomarin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_axesA

List the 7 WQuestions axes (Q who, O what, L where, T when, N how-much, K which, M how) and what each is for.

list_rolesA

List the canonical roles with their typed signatures. Unknown roles are also allowed (liberal policy) — you may invent domain roles freely.

add_entityC

Create an individual on a value axis (Q, O, L, T, N, or K).

define_verbA

Register a situation type (verb) and which roles it takes. Optional: assert_situation auto-registers unknown verbs permissively.

assert_situationA

Assert a fact: reify a situation for verb and attach its roles. Each role value is an existing entity id or an inline {id, axis, label}. valid_from/valid_to are ISO-8601, for facts that are only valid during a time range.

askC

Query by projection: fix some roles, ask for others. type filters to situations whose type matches the given category id (auto-registered verbs get the id action_<verb>). at (ISO) queries the model as it was valid at that time.

show_modelA

Dump the current universe: entity/fact counts and every fact.

load_exampleB

Load a prebuilt demo universe (e.g. "spa") to try queries instantly.

resetA

Clear the model and start a fresh empty universe.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.6/5.0

Scored across 9 tools

Disambiguation5/5

Each tool targets a distinct operation: adding entities, querying, asserting situations, defining verbs, listing axes/roles, loading examples, resetting, and showing the model. No overlap in functionality.

Naming Consistency4/5

Most tools follow a verb_noun pattern (add_entity, assert_situation, define_verb, list_axes, etc.), but 'ask' and 'reset' are single verbs, introducing minor inconsistency.

Tool Count5/5

9 tools is well-suited for a knowledge graph modeling server, covering core operations without being excessive or sparse.

Completeness3/5

Missing operations like updating or deleting specific entities or situations, and lacking targeted retrieval (e.g., get_entity by id) limit the completeness for a full lifecycle.

Maintenance

ActivityStale
ResponsivenessNo issues

Resources