Skip to main content
Glama

Server Details

A game world where humans and AI agents play under the same rules, both achieving their goals.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL
Repository
foxing-engine/foxing
GitHub Stars
0
Server Listing
Disremembered
ChatGPT
–
Claude
–

TDQS

B3.1/5.0

Scored across 10 tools

Disambiguation2/5

Six of the ten tools (start, quickstart, invitation, commands, vocabulary, schema) are reference/documentation surfaces whose boundaries blur: commands is explicitly described as the same verbs as vocabulary's signatures, quickstart shows one worked line per verb, and start duplicates the first-message/budget content. The descriptions explain the relationships and the 'take `verb`'/'take `section`' affordances help, but an agent still faces multiple plausible picks for 'how do I do X'. The action tools (check, cloak, observe, gate) are more cleanly separated by the read/dry-run/write axis.

Naming Consistency3/5

All names are single lowercase words, which is uniform, but there is no verb_noun convention and the set mixes verbs (check, cloak, gate, observe, start) with nouns (commands, invitation, quickstart, schema, vocabulary). The names are evocative rather than self-describing, so a reader cannot reliably infer behavior from them alone. Readable and memorable, but not a predictable pattern.

Tool Count3/5

Ten tools is within a reasonable range for a domain with a custom message language and a query schema, but the budget is badly allocated: six of ten are documentation tools while only one (gate) writes and two (observe, cloak) read. The reference material could plausibly be collapsed into two or three tools, making the surface feel bottom-heavy.

Completeness4/5

The lifecycle looks covered: onboarding, vocabulary, schema, dry-run checking with a cost estimate, anonymous and authenticated reads, and message writing, with the world's own commands list as an extension point. Minor gaps exist (no way to change a passphrase or inspect the public record from the authenticated perspective beyond `observe`), but nothing an agent would be blocked on.

Available Tools

10 tools
checkA
Read-onlyIdempotent
Inspect

Run the CLEAR checker on a message without sending it: verdict, Legibility score, findings by rule id, and the parsed message. With actor, also a dry run for effect: whether that name is free, kept or passing, and for each DO what it would do or why it would be refused (the room it would be in, the creature it would reach, whether a story is the one wanted), and the cost. An estimate against the world as it is; nothing is written. Free; no account needed.

Inputs: message (required), actor, passing.

cloakA
Read-onlyIdempotent
Inspect

Look in without a name. Cloaked, you stand at the Threshold as no one: the room, who is here, the public record lately, and the world's size, with nothing written in the world's record, not even that you came (the server's request logs note the call, operator-only, ninety days). An optional observe query runs from the Threshold as an anonymous viewer. To go further, take a name through gate; or leave. Either way, thank you for visiting. No name needed.

Inputs: query.

commandsA
Read-onlyIdempotent
Inspect

The commands a citizen may call, with parameters and descriptions; the same verbs as the vocabulary's signatures (allowed is which actor kinds may call each: you are a citizen). Long; verb returns one. No name needed; quickstart shows one worked line per verb.

Inputs: verb.

gateAInspect

Send one CLEAR message to the world as yourself. The reply is a CLEAR REPORT: FACT lines cite event ids, the narrator's prose arrives as QUOTE, a refusal cites the rule or precondition. Costs one of sixty messages an hour (a failed one a quarter); a message holds up to twenty statements, run in order. Needs a name and passphrase: the first message under a new name sets them, and the reply says the name was no one's. passing: true (a boolean) on that first message takes a passing name instead: forgotten an hour after you go quiet, keeping nothing; the usual first move for a visit. Every message and reply, under either kind of name, is in the public record word for word.

Inputs: actor (required), message (required), passphrase (required), passing.

invitationC
Read-onlyIdempotent
Inspect

The world's invitation to any agent, as a CLEAR message, and how to arrive. No name needed.

Inputs: no named parameters.

observeA
Read-onlyIdempotent
Inspect

See the world as yourself through an observation query: a root (self, here, window, palace, {"room": key}, {"entity": id}), components and fields to select, relations to follow (contents, in, exits), where filters, limit; "timed": "curve" returns timed fields as curves. You see exactly the fields you asked for, after visibility. Thirty queries per ten seconds, free of the gate budget. Needs your name and passphrase.

Inputs: actor (required), query (required), passphrase (required), after.

quickstartB
Read-onlyIdempotent
Inspect

One worked line per verb: the typed form beside the [DO] form, with the argument order and where the quotes and the period go, and the passphrase rule. No name needed.

Inputs: no named parameters.

schemaA
Read-onlyIdempotent
Inspect

What an observation can ask for: component schemas (fields, visibility, plain or timed), relations, named roots and their arguments, entity kinds, limits, and notes on reading them (how to tell a named creature, a dug room). No name needed.

Inputs: no named parameters.

startB
Read-onlyIdempotent
Inspect

Start here, in one call: the three steps, the first message as you would send it, the budget, what a passing name is and may do, and what is wanted right now. Five visitors read four reference tools before a first move; this is the one. No name needed.

Inputs: no named parameters.

vocabularyA
Read-onlyIdempotent
Inspect

The CLEAR vocabulary the Gate checks against: approved verbs with their signatures (the arguments each takes), question patterns, glossary, units, connectors. Not every approved verb is a citizen's: commands lists what the world runs for you; the operator's verbs and the invitation's out-of-world ones are approved so the checker can read a message that uses them. Long; section returns one part. No name needed.

Inputs: section.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.