Skip to main content
Glama

workbuddy_message_history

Read WorkBuddy local-assistant message history by message ID or pagination to review prior conversations, recover context, and support follow-up tasks.

Instructions

Read WorkBuddy local-assistant message history, either after a message ID or by pagination.

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": "workbuddy_message_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
messageIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It implies a read-only access pattern via 'Read' but says nothing about auth/permission needs, result ordering, page size behavior, what happens when both messageId and offset are supplied, or what the response looks like.

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?

A single front-loaded sentence with no filler; the resource comes first and the two modes are attached compactly. Brevity here is efficiency, not padding, though it leaves little room for the missing specifics.

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

Completeness2/5

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

With zero annotation coverage, no output schema, and three parameters at 0% schema coverage, the description should do far more. It omits precedence between messageId and offset, ordering of returned messages, and any sense of the return payload — all things an agent needs to page correctly.

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 0%, and the description does add real meaning for one parameter — 'after a message ID' clarifies messageId as an exclusive cursor rather than a lookup key. 'By pagination' loosely maps limit/offset, but their interplay with messageId and the result ordering remain undocumented, so compensation is only partial.

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?

States a specific verb ('Read') and resource ('WorkBuddy local-assistant message history'), and distinguishes two retrieval modes (after a message ID vs. pagination). It does not differentiate itself from potentially overlapping siblings such as clawbridge_events or codebuddy_job_transcript, but the resource is concrete enough to act on.

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 phrase 'either after a message ID or by pagination' hints at two modes but never says which situation selects which, nor when to prefer this over sibling history/event tools. No exclusions, no preconditions, no guidance on combining the modes.

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