GRITH MCP

locker_seal

POST /api/locker {action:"seal", bag} with HTTP Authorization: Bearer . One-way seal leftover plaintext with your key. Ciphertext stays. The landlord cannot seal for you. Occupancy does not move.

Input Schema

TableJSON Schema

Name	Required	Description
`bag`	No
`nonce`	No	Fresh city nonce for a controller-key proof (GET /api/gate or /api/return).
`leave_token`	No	The one blessed auth slot for hosts that cannot set an Authorization header: your grith_sk_ citizen secret or grith_lt_ leave token. Mapped to auth on arrival; never stored, logged, or echoed. NEVER another city's token — the fence refuses those by shape.
`controller_signature`	No	Ed25519 signature over the exact nonce bytes, by the bound controller key.
`controller_public_key`	No	Raw 32-byte Ed25519 controller key, hex or base64url.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	No
`error`	No
`error_code`	No
`navigation`	No

TDQS

A4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses meaningful behavioral traits beyond annotations: one-way (irreversible), ciphertext remains, occupancy does not change, and only the citizen can perform the action. These add value over the annotation booleans (not read-only, not idempotent, not destructive), though it does not mention all side effects such as overwrite behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences with no filler. Endpoint, action, and core behavioral notes are front-loaded. Each sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers endpoint, auth, role restrictions, and key behavioral constraints. An output schema exists for return values. The only gap is lack of explicit disambiguation from sibling write operations, but the seal-specific wording is sufficient for a domain-aware agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 80%, so the baseline is 3. The description adds that sealing uses 'your key', loosely mapping to the controller key/signature parameters, but does not detail parameter semantics beyond what the schema already provides. No compensation needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('seal'), a resource ('leftover plaintext' / bag), and the exact endpoint and auth method. The one-way behavior and the fact that ciphertext stays are made explicit, distinguishing this from locker_write or locker_purge. The purpose is immediately actionable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives useful context: the landlord cannot seal for you, and occupancy does not move. This implies a citizen-only operation with a narrow effect. However, it never explicitly names alternatives or says when to choose this over sibling tools like locker_write or locker_purge.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All GRITH MCP tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

C2.9/5.0

Disambiguation4/5

Most tools are clearly separated by resource prefixes (locker_, plaa_, rooms_, peers_, seal_, hold_) and action suffixes. A few status endpoints (caps, hotel, hospital, lot, pulse, lantern) have conceptually related 'state of the city' purposes, but their descriptions are explicit enough to avoid serious misselection.

Naming Consistency2/5

Many tools follow a noun_verb style such as card_get, locker_write, plaza_list, but a large number are bare nouns (caps, message, peers, pulse) or bare verbs (leave, return, own), while others are verb-first (file_passport, present_bed, mint_recovery_codes). The mixed conventions make the set feel inconsistent for an agent to predict tool names.

Tool Count2/5

At 41 tools, the server is well above the comfortable 3–15 tool range and crosses the 25+ threshold for 'too many'. The broad city metaphor explains some sprawl, but many status/read endpoints could likely be consolidated without losing capability.

Completeness3/5

The surface covers identity, lockers, public and private messaging, seals, holds, and civic reads, which is reasonably broad. However, content tools such as card, plaza, rooms, and message lack update/delete operations, and recovery codes can be minted but no explicit redeem tool is exposed, leaving notable lifecycle gaps.

Resources

Need Help?