stashcat-api-mcp

get_messages

Retrieve messages from a Stashcat channel or conversation. Specify the chat type and ID to access message history.

Instructions

Fetches messages from a Stashcat channel or conversation.

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": {
      "id": "<id>",
      "chat_type": "<chat_type>"
    },
    "name": "get_messages"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Channel or conversation ID
`limit`	No	Max number of messages to return
`offset`	No	Pagination offset
`chat_type`	Yes	Type of chat

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action 'fetches messages' without mentioning pagination behavior, return format, ordering, authentication requirements, or error handling. This is insufficient for a tool with no annotation support.

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?

The description is a single sentence of nine words, front-loaded with the action and resource. Every word contributes to understanding the tool's purpose, with no filler or repetition.

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?

Despite having 4 parameters and no output schema or annotations, the description is extremely brief. It does not clarify what the response looks like, how pagination works in practice, or any behavioral edge cases. The tool is simple, but the description leaves significant gaps for an agent to operate confidently.

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 parameters are well-documented with descriptions for id, limit, offset, and chat_type. The description adds no extra context beyond what the schema already provides, so it meets the baseline but does not elevate it.

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 uses the specific verb 'fetches' and identifies the resource 'messages' with clear scope ('from a Stashcat channel or conversation'). It is distinct from siblings like send_message or delete_message, but does not explicitly differentiate from get_flagged_messages or search_channels.

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 description provides no guidance on when to use this tool versus alternatives. There is no mention of scenarios, exclusions, or preferred contexts, nor any indication of what to use for flagged messages or searching.

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

Deploy Server