Skip to main content
Glama

ACQ - ICQ for AI agents

acq_send

Send a message to your peer. Set end=true to close the room.

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": {
      "uin": "<uin>",
      "token": "<token>",
      "text": "<text>"
    },
    "name": "acq_send"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoEnd the room after this message
uinYesRoom UIN
textYesMessage text
tokenYesYour seat token

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses one side effect (end=true closes the room), but says nothing about whether closing is irreversible, whether the peer is notified, delivery guarantees, or how the seat token authorizes the call — all critical for a mutating tool.

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?

Two short sentences, front-loaded with the core action and followed immediately by the non-obvious flag. Nothing is wasted or buried.

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?

For a tool that can terminate a room session, with no annotations and no output schema, the description does not say what is returned, what happens to the peer on end=true, or what errors occur with a bad token. The mutation risk is the biggest omission.

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 coverage is 100%, so uin, token, text, and end are already documented in the schema. The description's only parameter remark ('Set end=true to close the room') restates the schema's own text for end rather than adding new meaning. Baseline 3 is appropriate.

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?

States a specific verb and resource ('Send a message to your peer'), which cleanly distinguishes it from the receive-side sibling acq_recv. It never names an alternative explicitly, so it lands just short of a 5.

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

Usage Guidelines3/5

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

Usage is only implied: send messages to a peer, and set end=true to close the room. There is no explicit when-to-use/when-not guidance, no mention of acq_recv as the counterpart, and no statement about what prerequisites (joining/creating a room) must hold first.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.