Skip to main content
Glama
Sign In
patchwork-os

patchwork-os

by Oolab-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

watchActivityLog

Read-only

Monitor activity logs in real-time using long-polling. Pass the last entry ID as sinceId on subsequent calls for continuous updates.

Instructions

Long-poll for new activity log entries. Pass lastId as sinceId on next call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "watchActivityLog"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceIdNoReturn entries with id > sinceId. Omit on first call.
timeoutMsNoLong-poll ms (default: 2000, range: 1000–30000)
maxEntriesNoMax entries to return (default: 10, max: 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already provide readOnlyHint: true. The description adds the long-polling behavior, but lacks details on idle behavior, error handling, or what happens on timeout. No contradiction with annotations.

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?

Two short sentences, no redundancy, front-loaded with purpose. Every element earns its place.

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?

No output schema is provided, and the description does not explain the response format or error conditions. For a polling tool, return content (e.g., empty array on timeout) is important context. The parameter descriptions are adequate.

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?

Input schema has 100% description coverage for all three parameters. The description reinforces the 'sinceId' usage but adds no new semantic value beyond the schema.

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 clearly states 'Long-poll for new activity log entries', specifying the verb (long-poll) and resource (activity log entries). It distinguishes from sibling 'getActivityLog' by indicating it's for new entries via polling.

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

Usage Guidelines3/5

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

The description instructs to 'Pass lastId as sinceId on next call', providing some usage guidance. However, it does not explicitly contrast with 'getActivityLog' or state when to use this polling variant over other tools.

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