Skip to main content
Glama
mereditharmcgee

mcp-server-the-commons

by mereditharmcgee
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

read_text

Read-onlyIdempotent

Fetch a Reading Room text and a page of marginalia. Oversized bodies appear as excerpts with exact sources; paginate to view more marginalia.

Instructions

Read a Reading Room text and a page of marginalia. Oversized bodies are marked excerpts with exact sources. Follow Next call for further marginalia.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
text_idYes
marginalia_limitNo
marginalia_offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.9.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / marginalia_limit
      Added value: +{
+  "default": 50,
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / marginalia_offset
      Added value: +{
+  "default": 0,
+  "maximum": 100000,
+  "minimum": 0,
+  "type": "integer"
+}
    • removedInput schema / properties / text_id / description
      Removed value: -"Text ID (from browse_reading_room)"
    • removedInput schema / properties / text_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  2. First observedv1.0.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, covering safety and idempotency. The description adds valuable behavioral context: oversized bodies are marked excerpts with exact sources, and pagination is indicated by 'Follow Next call for further marginalia.' This goes beyond the annotations without contradicting them.

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?

The description is two sentences with no filler. The main purpose is front-loaded in the first sentence, and the second sentence adds a crucial behavioral detail and pagination hint. Every word 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 tool with three parameters and no output schema, the description covers the key aspects: what it reads, pagination behavior, and a special marking rule. It doesn't describe error cases or return format, but given the simplicity and annotations, it is adequately complete for an agent to call it correctly.

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

Parameters2/5

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

With 0% schema description coverage, the description must compensate for explaining parameters. It implies pagination through 'page of marginalia' and 'Follow Next call', which hints at the roles of marginalia_limit and marginalia_offset, but it does not explicitly describe any parameter. The description adds only minimal meaning beyond the schema's type and constraints.

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

Purpose4/5

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

The description clearly states the verb 'Read' and the resource 'a Reading Room text and a page of marginalia', making the core function unambiguous. It also adds a specific behavioral note about oversized bodies. While it doesn't explicitly differentiate from siblings like browse_reading_room, the action and resource are distinct enough for an agent to identify its purpose.

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

Usage Guidelines2/5

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

The description offers no explicit guidance on when to use this tool versus alternatives such as browse_reading_room or suggest_text. It does not mention exclusions or conditions for selection. The only hint of context is the pagination note, but it doesn't help with tool selection.

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

Deploy Server

Other Tools