AccountHub

share_direct_chat_items

Idempotent

Copy only the selected direct-chat messages into the selected shared project after the user reviewed the preview and its recipient scope. Supply expected_members and expected_items unchanged from preview. No other chat history or reply/private references are copied.

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": {
      "chat_id": "<chat_id>",
      "project_id": "<project_id>",
      "item_ids": "<item_ids>",
      "expected_members": "<expected_members>",
      "expected_items": "<expected_items>"
    },
    "name": "share_direct_chat_items"
  }
}

Input Schema

Name	Required	Description	Default
`chat_id`	Yes
`item_ids`	Yes
`project_id`	Yes
`expected_items`	Yes
`expected_members`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 26, 2026
- removedInput schema / properties / expected_items / items / properties / body / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedInput schema / properties / expected_items / items / properties / body / type
```
Added value: +[
+  "string",
+  "null"
+]
```
AddedOct 19, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With annotations already indicating idempotent and non-destructive behavior, the description adds useful safety context: only selected items are copied, no other chat history or reply/private references are copied, and expected values must match the preview. It does not explain mismatch handling or permission requirements, but it meaningfully extends the annotation-provided safety profile.

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 three tight sentences, front-loads the core action and scope, then adds the required preview handoff and exclusion rules. There is no filler.

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

Completeness4/5

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

For a five-parameter mutation with no output schema and sparse annotations, the description covers the key workflow prerequisite, expected-value handoff, and what is not copied. It could say more about failure behavior when expected values do not match, but it is largely complete for correct invocation.

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 0%, so the description must compensate. It maps chat_id/item_ids to selected direct-chat messages, project_id to the selected shared project, and explains expected_members and expected_items as unchanged values from preview, but it does not detail expected_items' object structure, expected_members format, UUID expectations, or item limits.

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: copy only selected direct-chat messages into the selected shared project. It also clarifies scope by excluding other chat history and reply/private references, which distinguishes it from broader sharing or forwarding tools.

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 clearly establishes the prerequisite that the user must first review the preview and recipient scope, and that expected_members and expected_items must be supplied unchanged from that preview. It does not explicitly name preview_direct_chat_share as the required prior tool, but the workflow is strongly implied.

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?