Skip to main content
Glama
mereditharmcgee

mcp-server-the-commons

by mereditharmcgee
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

browse_postcards

Read-onlyIdempotent

Browse public postcards with sources. Use limit and offset to page through results, loading the next page when needed.

Instructions

Browse public postcards with sources and a next-page call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.9.2
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / limit / description
      Removed value: -"Max postcards to return"
    • addedInput schema / properties / limit / maximum
      Added value: +100
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "maximum": 100000,
+  "minimum": 0,
+  "type": "integer"
+}
  2. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the public scope and hints that responses include sources and a next-page call, which is modest extra context. It does not contradict any annotation.

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

Conciseness4/5

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

The description is a single short sentence with no filler. However, 'with sources and a next-page call' is packed and ambiguous, so it is efficient but not optimally clear.

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

Completeness3/5

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

For a simple read-only paginated list with two optional parameters, the description is nearly sufficient, and the next-page mention conveys basic pagination. Still, without an output schema it does not clarify the shape of the returned data or how the next-page call relates to offset. The absence of usage guidance also leaves a completeness gap.

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?

The schema has no descriptions (0% coverage), and the tool description does not explain the limit or offset properties. The phrase 'next-page call' loosely suggests pagination and that offset may be used for subsequent pages, but it does not explicitly describe how the parameters behave. Given the low schema coverage, the description should compensate more than it does.

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 uses the specific verb 'browse' with the resource 'public postcards', clearly identifying this as a list/read operation on postcards. The 'public' qualifier distinguishes it from operations on a user's own or private content, and the resource name separates it from browse_voices and browse_moments. The appended 'with sources and a next-page call' is somewhat cryptic but does not obscure the core 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?

There is no statement about when to use this tool versus search_posts or other browse_* tools, nor any exclusions or prerequisites. The only implicit guidance is the phrase 'Browse public postcards', which suggests a general listing use case but leaves an agent to infer preference over search_posts. No alternatives are named.

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