Skip to main content
Glama
Sign In

AccountHub

by ai.accounthub
OverviewDiscussionsAdmin

create_chatwork_draft

Prepare a Chatwork message WITHOUT sending it: checks the account is a member of the room and returns the final body plus a draft_fingerprint. Nothing is posted. Show the room and the exact body to the user and get an explicit yes, then call send_chatwork_message with the same body and the fingerprint. The fingerprint only proves the text is unchanged — it is not the user's approval.

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": {
      "room_id": "<room_id>",
      "body": "<body>"
    },
    "name": "create_chatwork_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesMessage body (Chatwork notation such as [To:123] is kept as-is).
accountNoChatwork account label (see list_accounts). Required when more than one Chatwork account is connected and connection_id is not given.
room_idYesChatwork room id (digits, from list_chatwork_rooms).
reply_toNoReply to this message: prepends [rp aid=<account_id> to=<room>-<message_id>].

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotation destructiveHint=false, the description discloses important behavior: it checks room membership, returns the final body and a draft_fingerprint, and does not post anything. It also explains the fingerprint's limited meaning, which is crucial for correct downstream use.

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 four tight sentences, front-loads the no-send guarantee, and then gives the required workflow. Every sentence carries operational value, especially the fingerprint caveat.

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?

Although there is no output schema, the description explains the key return values: final body and draft_fingerprint. It also supplies the necessary safety and workflow context for an agent to call the tool 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 100%, so the schema already documents all four parameters, including account and reply_to. The description reinforces body and room usage but does not add syntax or meaning beyond what the schema provides.

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: prepare a Chatwork message without sending it. It also clarifies the key effect that nothing is posted and distinguishes the tool from send_chatwork_message by explaining the draft-and-confirm workflow.

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

Usage Guidelines5/5

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

The description gives explicit usage guidance: show the room and exact body to the user, get an explicit yes, then call send_chatwork_message with the same body and fingerprint. It also warns that the fingerprint is not user approval, which prevents a likely misuse.

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

All AccountHub toolsInspect
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