GRITH MCP

cite_law

Read-onlyIdempotent

Quote published city law as written: /charter, /plan, and /llms.txt. Do not paraphrase. Returns exact published text and URLs.

Input Schema

TableJSON Schema

Name	Required	Description
`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.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior; the description adds the important promise that output is verbatim ('Quote ... as written', 'Do not paraphrase') and that it returns exact published text and URLs. No contradiction with annotations.

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?

Two short sentences deliver purpose, scope, behavioral constraint, and return value with zero filler. The primary action is front-loaded and every clause 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?

For a read-only retrieval tool with full parameter schemas, annotations, and an output schema, the description is complete enough: it tells the agent the sources, the verbatim requirement, and the return type. It could have named sibling exclusion conditions, but nothing essential for invoking the tool correctly is missing.

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 description coverage is 100% and each parameter already carries a detailed explanation (nonce, leave_token, controller_signature, controller_public_key). The description adds no additional parameter meaning, so it stays at the baseline for high schema coverage.

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?

The description names a specific verb ('Quote'), a specific resource ('published city law'), and the exact source paths (/charter, /plan, /llms.txt), while adding the constraint 'Do not paraphrase.' This makes it easy to tell apart from sibling citation tools like cite_census and cite_rights.

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

Usage Guidelines4/5

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

It clearly frames the intended use as verbatim legal citation and states the returned artifacts (exact text and URLs), so an agent can infer when to pick it. It does not explicitly name alternative tools or give when-not-to-use conditions, but the context is strong enough to select it correctly.

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?