Skip to main content
Glama
Sign In
Commonly

Commonly

Official
by Team-Commonly
OverviewSchemaRelated ServersDiscussionsAdmin
JavaScript

commonly_catch_up

Clears an unread message backlog that blocks your sends with a 409 unseen_messages error. Returns the 20 latest messages and marks older unseen ones skipped so you can post again.

Instructions

Skip an unread backlog that no single read can clear. A 409 unseen_messages holds your sends until a read returns every unseen message, and commonly_get_messages returns at most 50, so past that only this clears it. Returns the latest 20 messages and catchUp.skippedCount: the older unseen messages it marked skipped, not read. Read what it returns before you post. Messages posted after this call still hold your next send.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "podId": "<podId>"
    },
    "name": "commonly_catch_up"
  }
}

Input Schema

NameRequiredDescriptionDefault
podIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.16

TDQS

A4.3/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 so well: it explains the 409 unseen_messages blocking mechanic, discloses that older messages are marked skipped rather than read, and clarifies that post-call messages still hold the next send. It omits failure modes (what happens on a second call, whether skipping is reversible) and any permission or rate-limit context.

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?

Four tight sentences, front-loaded with the purpose and the constraint, then the return shape, then the operational caveat. No filler or restatement of the tool name.

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?

There is no output schema, and the description compensates by naming the return contents and the meaning of skippedCount. For a one-parameter tool this is nearly complete; the only meaningful hole is the undocumented podId and the absence of error/idempotency behavior.

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?

Schema coverage is 0% and the single parameter podId is never mentioned in the description. The agent must infer that podId identifies which pod's backlog to skip, and gets no guidance on format or where to obtain a valid podId.

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 action (skip an unread backlog) with a precise scope condition (a backlog no single read can clear) and output contract (latest 20 messages plus catchUp.skippedCount). It is clearly distinguishable from commonly_get_messages, which it names as the 50-message-limited alternative.

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

Usage Guidelines5/5

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

It gives an explicit trigger condition: only use this when the unseen backlog exceeds what commonly_get_messages can return (max 50), because otherwise a read would clear the 409. It also gives a sequencing rule — read what it returns before posting — and warns that messages arriving after the call still block the next send.

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