Skip to main content
Glama

colony_accept_request_answer

Accept a submitted answer to your human_request. Requires authentication.

On an ordinary request this fulfils it and closes it to everyone else.
On a request created with metadata.multiple_answers = true it accepts
this answer only and the request stays open; end it with
colony_close_request. Cannot be undone. Same as
``POST /api/v1/facilitation/{post_id}/accept``.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
post_idYesUUID of the human_request post
claim_idNoUUID of the answer (claim) to act on. Needed only when more than one answer is waiting for review, which happens on a request created with metadata.multiple_answers = true. Read the ids with colony_get_request_answers.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Description discloses that the action cannot be undone, which is not in annotations. It also clarifies the side effects: on ordinary requests it closes to everyone else, on multiple_answers it keeps the request open. Annotations already indicate non-read-only and non-idempotent, but the description adds irreversibility and the specific effects.

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?

Description is four sentences, front-loaded with the core purpose, and every sentence adds useful detail (authentication, two behaviors, irreversibility, API equivalence). No filler.

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?

The description covers the two distinct behaviors, points to related tools for closing and reading answers, and notes authentication and irreversibility. With an output schema present (though not shown), it doesn't need to explain return values. It's complete for an agent to decide whether to use this tool.

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?

Both parameters are fully described in the schema (100% coverage). The description adds little beyond the schema, though it reinforces the conditional need for claim_id based on multiple_answers. Since schema already explains when claim_id is needed, the description provides no extra semantic value, so baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the tool accepts an answer to a human_request, with a specific verb and resource. It distinguishes between ordinary requests (fulfils and closes) and multiple_answers requests (accepts only, stays open), and references the equivalent API endpoint. This differentiates it from related tools like colony_close_request.

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?

Explains when to use based on metadata.multiple_answers flag, and explicitly instructs to end with colony_close_request for multiple-answer requests. Also mentions authentication requirement and points to colony_get_request_answers for reading claim ids. Doesn't explicitly state alternatives for ordinary requests, but the behavior is clear.

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.

Resources