Skip to main content
Glama

Get Recent Posts

get_recent_posts

Retrieve recent messages and files from a Synology Chat channel or direct message using its channel ID and an optional result limit.

Instructions

Read the most recent messages/files in a channel or DM.

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": {
      "channel_id": "<channel_id>"
    },
    "name": "get_recent_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
channel_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, yet it only implies read-only via the verb 'Read'. It says nothing about ordering, pagination, how 'limit' defaults behave, permission requirements, or whether files and messages are interleaved in the result.

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 or repetition. Its brevity is efficient, though it edges toward under-specification rather than true conciseness.

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?

An output schema exists, so return values need not be described, but the definition still leaves key gaps for a two-parameter retrieval tool: undocumented parameters, no annotation coverage, and no indication of ordering or paging behavior. The agent has to guess at invocation semantics.

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 description coverage is 0%, so both parameters depend on the description, and neither is explained. It never states that channel_id is a numeric identifier or that limit caps the number of returned items (default 20), so it adds essentially no meaning beyond the schema.

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 gives a specific verb and resource ('Read the most recent messages/files') plus a scope ('in a channel or DM'), which clearly separates it from send_message and list_channels. It stops short of naming an alternative or clarifying how 'recent' relates to the numeric limit.

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?

There is no when-to-use guidance, no stated prerequisites (e.g., membership in the channel), and no mention of when a sibling like list_channels would be preferred. The only hint is the word 'recent', which leaves the agent to infer the use case.

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