Skip to main content
Glama

peck-mcp

by io.github.kryp2
OverviewDiscussionsAdmin

peck_user_posts

View everything a specific address has written on the BSV social graph. Convenience wrapper over peck_feed with author filter — returns posts in newest-first order as {author, keys, items, next}: the resolved identity, every key whose posts are included (an identity signs with more than one), and the page of posts. There is no total count. Use when you want to understand who someone is and what they have been saying across all apps.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appNoOptional: restrict to a single app.
typeNoOptional: only show this type (post, reply, like, ...).
limitNoMax items (default 20, max 100).
cursorNoPagination cursor: the `next` object of the previous page, sent back unchanged. Omit for the first page. Prefer it over offset.
offsetNoLegacy pagination offset (max offset+limit 1000). Use `cursor` instead.
addressYesBSV address of the author (a public key or @handle also works).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / address / description
      Previous value: -"BSV address of the author."New value: +"BSV address of the author (a public key or @handle also works)."
    • addedInput schema / properties / cursor
      Added value: +{
+  "additionalProperties": true,
+  "description": "Pagination cursor: the `next` object of the previous page, sent back unchanged. Omit for the first page. Prefer it over offset.",
+  "type": "object"
+}
    • changedInput schema / properties / offset / description
      Previous value: -"Pagination offset."New value: +"Legacy pagination offset (max offset+limit 1000). Use `cursor` instead."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose meaningful behavior beyond the schema: newest-first ordering, the resolved identity, the fact that an identity signs with more than one key, and that there is no total count. It omits read-safety/auth expectations and pagination edge behavior, which keeps it from a 5.

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?

It is front-loaded with the purpose and the wrapper relationship before enumerating the return shape; the middle sentence is long but every clause (keys, no total count, page) earns its place. Slightly dense but no filler.

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?

With no output schema, the description correctly compensates by describing the returned shape {author, keys, items, next} and the absence of a total count. It is essentially complete for invocation, though it does not explicitly address the cursor-vs-offset relationship that the schema relies on.

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%, so the schema already documents app, type, limit, cursor, offset, and address. The description adds only the high-level notion of an author filter and does not clarify parameter interactions, so the baseline 3 applies.

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 states a specific verb and resource ("View everything a specific address has written on the BSV social graph") and explicitly positions the tool as a wrapper over peck_feed with an author filter, which distinguishes it from that sibling without opening either schema.

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 gives a clear selection condition: use this when you want to understand who someone is and what they have been saying across all apps, contrasted with the underlying peck_feed wrapper. It stops short of naming explicit when-not cases or pointing to peck_profile for identity-only queries.

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

All peck-mcp toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources