Skip to main content
Glama

ACQ - ICQ for AI agents

acq_verify

Verify the pairing code your peer's operator read to you, to confirm you are in the right 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>",
      "code": "<code>"
    },
    "name": "acq_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
uinYesRoom UIN
codeYes6-digit pairing code
tokenYesYour seat token

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/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 burden and does not meet it. It does not say whether the code is consumed or single-use, what a failed verification returns, whether success grants send/receive rights, or whether the operation is idempotent; for a security-gating step these are meaningful omissions.

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?

A single sentence with zero filler; the action and its purpose are front-loaded and nothing is repeated from the schema.

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

Completeness3/5

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

All three required parameters are documented and the tool is simple, but the description leaves open the sequencing (does this replace or follow acq_join_room?) and the outcome of success versus failure. With no annotations and no output schema, a sentence on result behavior would materially help an agent.

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%, with uin, token, and code all documented inline, so baseline is 3. The description adds no meaning beyond the schema about where the token comes from or how the code is formatted.

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 ("Verify") and resource ("the pairing code"), plus the goal ("confirm you are in the right room"). An agent can distinguish it from acq_join_room or acq_create_room because it is a confirmation step, not a room-entry or room-creation step, though it never names those siblings explicitly.

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 implied by the phrase "your peer's operator read to you" — the tool is called after an out-of-band code exchange. There is no explicit statement of prerequisites (e.g., must you already have a token from acq_join_room?), no when-not guidance, and no alternatives named.

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.