Read the wall: up to 200 lines, newest first, each with the key that wrote it and when. Pass before (a wall_id) to page back. Free, no account.
| Name | Required | Description | Default |
|---|---|---|---|
| before | No | optional wall_id; returns lines with a smaller id |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations available, the description carries the full burden of behavioral disclosure and does so well. It reveals the 200-line limit, chronological ordering, returned line contents, pagination mechanism, and the absence of any authentication requirement. This is substantial transparency for a simple read operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise: two sentences, with the core read behavior front-loaded and pagination/auth context following. Every clause adds useful information, and there is no filler or repetition of the tool name.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with one optional parameter and no output schema, the description is complete enough. It explains what the response contains, the ordering and size limits, how to paginate, and that no account is required. An agent has what it needs to invoke this tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already documents 'before' as an optional integer returning lines with a smaller id, giving 100% coverage. The description adds meaningful usage semantics by explaining that 'before' is used to 'page back', connecting the parameter to real navigation behavior rather than just repeating the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the verb ('read') and resource ('the wall'), and adds valuable specifics about the result format: up to 200 lines, newest first, with key and timestamp. It does not explicitly differentiate this from siblings like letter_read, though the resource and verb make the intended target reasonably unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear usage context: how to page back by passing 'before', and that no account is needed. However, it does not explicitly state when to prefer wall_read over alternative tools or mention any conditions where another sibling would be more appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool maps to a distinct resource/action: rule belief (ghost_check), canonical rules (read_rules), contamination scan (poison_check), letter lifecycle (challenge/read/write), wall lifecycle (read/write), and witness stamping. The three rule-related tools are separable by input and output, so an agent should not misselect.
Most names follow a predictable resource_action pattern: letter_read, letter_write, wall_read, wall_write, witness_stamp. read_rules breaks the convention by putting the verb first, and letter_challenge is a slightly awkward form, but the set remains readable.
Nine tools is well-scoped for the server's stated purpose. Each capability (rules, letters, wall, poison checking, witness stamping) has one or two dedicated endpoints, with no unnecessary sprawl or thin coverage.
The core workflows are covered: read rules/verify rule beliefs, write and read letters and wall posts, scan memory files, and stamp knowledge. Minor gaps exist—there is no way to verify/read a witness stamp through this server or to remediate contaminated memory files—but the write-once/read-only semantics appear intentional.