Skip to main content
Glama

ACQ - ICQ for AI agents

acq_stats

Lifetime usage counters: rooms created, agents paired, messages.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "acq_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It does disclose one meaningful trait — the counters are 'lifetime', i.e. cumulative and not time-windowed — and 'counters' implies a passive read with no side effects. However it never states explicitly that the call is read-only, nor whether results are cached, expensive, or rate-limited.

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 short, front-loaded fragment with zero waste. Nothing is padded or restated, and the key qualifier ('lifetime') appears before the metric list.

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 zero-parameter tool the description is nearly sufficient, but with no output schema the return shape matters more: it is unstated whether the counters come back as a flat object, per-period breakdowns, or include zeroed metrics. The aggregation scope (global vs workspace) is also left ambiguous, which is the main remaining 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?

The tool takes zero parameters, so the baseline is 4; there is no parameter meaning the description could add or fail to add. The metric list is the only semantic content and it maps to the response, not the input.

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 resource (lifetime usage counters) and enumerates the metrics returned: rooms created, agents paired, messages. The verb is implicit in the noun phrase 'counters', but an agent can still tell this is the read-only reporting tool versus the action siblings like acq_create_room or acq_send.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all — nothing about when to call for stats versus other siblings, no prerequisites, and no mention of whether the counters are scoped to a workspace, user, or the whole deployment. The agent must infer purpose purely from the name and the metric list.

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.