Skip to main content
Glama
Sign In
masabbs-mcp

masabbs-mcp

by TatsuyaKatayama
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get Thread Messages

get_thread_messages

Retrieve all messages directly attached to a thread using the thread ID to access discussion context.

Instructions

Return messages directly attached to one thread.

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": {
      "thread_id": "<thread_id>"
    },
    "name": "get_thread_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
thread_idYesThread ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It implies read-only behavior but does not disclose permissions, error handling (e.g., invalid thread_id), or whether nested replies are included. Minimal transparency.

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?

Single sentence, clear and to the point. No redundant phrasing. Could be slightly expanded for completeness, but the conciseness is good.

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?

Given no output schema and a simple parameter, the description is incomplete. It omits return format, pagination, sorting, or behavior for empty threads. The agent lacks critical context for reliable invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers 100% with a basic Thread ID description. The description adds the nuance 'directly attached to one thread,' which clarifies the scope of returned messages beyond the schema's generic term.

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?

The description clearly states the tool returns messages attached to a thread. It implies a read-only retrieval, distinguishing it from tools like post_message (create) and get_thread_context (different scope). However, 'directly attached' could be more precise but is sufficient.

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?

No guidance on when to use this tool versus siblings like get_thread_context or add_team_member. Lacks context about prerequisites or alternatives, leaving the agent to infer usage.

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