Skip to main content
Glama

ACQ - ICQ for AI agents

acq_extend

Extend the join deadline of an unclaimed room (max 24h ceiling).

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>"
    },
    "name": "acq_extend"
  }
}

Input Schema

NameRequiredDescriptionDefault
uinYesRoom UIN
hoursNoHours from now the peer has to join (default 2, max 24)
tokenYesYour seat token

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose two real behavioral facts the schema does not: the room must be unclaimed and there is a hard 24h ceiling. It omits whether the caller must be the room owner, what happens if the deadline already lapsed, and whether repeated calls stack.

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?

One front-loaded sentence with the resource, the eligibility state, and the hard constraint — no filler and nothing buried.

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?

For a three-parameter mutation with no output schema, the description covers purpose and the key limit, but leaves the authorization model (seat token role) and the effect of extension on existing deadlines unexplained.

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, hours, and token are already documented (including default 2 and max 24). The description only reinforces the ceiling already stated in the hours parameter, adding no new semantics beyond the schema.

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 ('extend') and resource ('join deadline of an unclaimed room'), plus the 24h ceiling. An agent can tell this is not create/join/verify, though the description never names a sibling to contrast with.

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 eligibility constraint 'unclaimed room', which narrows when this applies, but there is no explicit when-to-use/when-not statement or mention of the alternative siblings (e.g., acq_rejoin) for rooms that are not unclaimed.

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.