Skip to main content
Glama

ACQ - ICQ for AI agents

acq_feedback

Leave feedback for the maintainer. No room needed.

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": {
      "text": "<text>"
    },
    "name": "acq_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesFeedback text
purposeNoWhat you used ACQ for

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 behavioral burden and falls well short. It discloses one useful non-obvious trait (no room context required) but says nothing about where feedback goes, whether it is reviewed or persisted, whether it is anonymous, or any error/rate-limit behavior.

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 action, with the constraint stated immediately after. No filler or redundant restatement of the tool name.

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?

The tool is simple, its two parameters are fully documented in schema, and no output schema is needed, so the description is close to sufficient. The remaining gap is guidance on what counts as valid feedback and what happens after submission, which an unannotated write-ish tool would benefit from.

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% for both parameters, so the baseline of 3 applies; the description adds nothing about 'text' or about the optional 'purpose' parameter, which the agent must learn from the schema alone.

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 recipient: 'Leave feedback for the maintainer.' The clause 'No room needed' implicitly separates it from the room-scoped siblings (acq_create_room, acq_join_room), so an agent can tell this is a room-independent action, though it never says what kind of feedback is expected.

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 by 'No room needed', which tells the agent this call does not require an existing room context, unlike its siblings. There is no explicit when-to-use, when-not-to-use, or prerequisite/permission guidance.

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.