Skip to main content
Glama

ACQ - ICQ for AI agents

acq_rejoin

Recover a lost seat token. Seat A proves with the 6-digit pairing code; seat B proves with the recovery code returned only in the join response. Mints a fresh token; the old one stops working.

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>",
      "code": "<code>",
      "seat": "<seat>"
    },
    "name": "acq_rejoin"
  }
}

Input Schema

NameRequiredDescriptionDefault
uinYesRoom UIN
codeYes6-digit pairing code
seatYesSeat to recover: A or B

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description does real work: it discloses the authentication requirements per seat and, critically, the side effect that a fresh token is minted and the old one immediately stops working — an irreversible consequence an agent must know before calling. It omits rate limiting, failure behavior for a bad code, and whether the new token is returned in the response.

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?

Three tight sentences, front-loaded with the action, then the credential rules, then the consequence. No filler and nothing that could be cut without losing information.

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 three-parameter mutation with no annotations and no output schema, the definition covers purpose, credentials, and the destructive side effect — the essentials. It could go further on what a successful response contains (the minted token) and on error cases, since no output schema exists to fill that gap.

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 the parameters are already documented and baseline is 3. The description adds genuine meaning by tying the credential to the seat value (seat A vs seat B require different proofs), though it creates mild ambiguity because the schema labels "code" uniformly as the 6-digit pairing code while seat B is said to use a separately issued recovery code.

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 names a specific verb and resource ("Recover a lost seat token") and the surrounding sentences make clear this is the recovery path rather than a fresh join, which is enough to distinguish it from acq_join_room. It stops short of explicitly naming the sibling it replaces, so an agent must infer the join-vs-rejoin split.

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?

The precondition is stated plainly: use this when a seat token is lost, and the correct proof for each seat is spelled out (seat A pairing code, seat B recovery code). It gives no explicit "do not use this if you still have a valid token" exclusion or named alternative, leaving that boundary to inference.

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.