AccountHub

search_chatwork_messages

Read-only

Search Chatwork messages across ALL connected Chatwork accounts by keyword (case-insensitive substring of the body or sender name). API limit: Chatwork has no search endpoint and no full-text search, so this scans only the latest 100 messages of each of the most recently active rooms (max_rooms, default 10, max 30) — older messages are NOT found. coverage/limits in the result says exactly what was scanned.

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": {
      "query": "<query>"
    },
    "name": "search_chatwork_messages"
  }
}

Input Schema

Name	Required	Description
`query`	Yes	Keyword (empty string = list the scanned messages).
`accounts`	No	Chatwork account labels. Omit for every connected Chatwork account.
`room_ids`	No	Only scan these room ids.
`max_rooms`	No	How many recent rooms to scan per account (default 10, max 30).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 24, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses a critical behavioral limitation: Chatwork has no search endpoint, so the tool scans only the latest 100 messages per recent room and may miss older content. It also explains max_rooms defaults and that `coverage`/`limits` in the result report exactly what was scanned.

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 front-loaded with the core action and scope, then follows with the key API limitation and result-coverage note. Every sentence adds useful information without repetition or filler.

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

Completeness5/5

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

For a read-only search tool with a fully described input schema and no output schema, the description supplies the critical limitation, scan scope, and result-coverage behavior an agent needs to invoke it correctly and interpret its findings.

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 coverage is 100%, so baseline would be 3, but the description adds useful semantics for `query` (case-insensitive substring of body or sender name) and contextualizes `max_rooms` as controlling how many recent rooms are scanned. The remaining parameters are already well documented in 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 states a specific verb and resource ("Search Chatwork messages") plus the exact scope ("across ALL connected Chatwork accounts by keyword"). It clearly distinguishes itself as a Chatwork-specific search rather than a generic message search, and the keyword semantics are defined inline.

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

Usage Guidelines4/5

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

It gives clear usage context by explaining that only the latest 100 messages in recent rooms are scanned and that older messages are NOT found. However, it does not explicitly name alternatives for older-message or broader searches, so the guidance is strong but not complete.

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

All AccountHub tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?