Skip to main content
Glama
Sign In

GenFlick

by com.genflick
OverviewDiscussionsAdmin

Answer Work Question

answer_work_question
DestructiveIdempotent

Answer or skip one exact open decision of the work or of one of its tasks, by option or in the creator's words, and resume only within the existing approved scope and budget; may resume paid work. Several decisions can be open at once; answer them in any order.

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": {
      "work_id": "<work_id>",
      "decision_id": "<decision_id>",
      "expected_revision": "<expected_revision>",
      "request_key": "<request_key>"
    },
    "name": "answer_work_question"
  }
}

Input Schema

NameRequiredDescriptionDefault
skipNoTrue when the creator skips this question: the agent keeps its stated assumption, or decides for itself. Give skip alone.
answerNoCreator's own words for this specific decision. Give option_ids, answer or both.
work_idYesOpaque authorized product identifier; never proof of access.
option_idsNoIDs of the options the creator chose from the Decision's options.
decision_idYesOpaque authorized product identifier; never proof of access.
request_keyYesStable caller request key; reuse unchanged after a lost response.
expected_revisionYesExact revision returned with the current open Decision, not the Work revision. The decision must still belong to this work and cannot enlarge approved scope or budget.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveness, idempotency and closed-world behavior, but the description adds context annotations cannot: that answering may resume paid work and that resumption is confined to previously approved scope and budget. That cost/authority implication is genuinely useful for an agent deciding whether to answer autonomously.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One dense, front-loaded sentence covering mode, scope and resumption, plus a short clarifying sentence on multiplicity. The semicolon-chained clauses make it slightly harder to parse than it needs to be, but nothing is padding.

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?

For a destructive, idempotent mutation with a full schema, full parameter descriptions and an output schema, the description supplies the remaining decision-relevant context: scope/budget limits and the existence of multiple concurrent decisions. Revision-conflict handling is left implicit in expected_revision's schema text, which is acceptable.

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 the baseline is 3. The phrase 'by option or in the creator's words' echoes the schema's own 'Give option_ids, answer or both' and 'Give skip alone', adding little beyond what the parameter descriptions already say.

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 pair (answer or skip) and resource (one exact open decision of a work or task), plus the dual input mode (by option or creator's words). It is distinguishable from raise_work_question and settle_questions by its explicit 'one exact open decision' scope, though it never names those siblings.

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?

Gives ordering guidance ('several decisions can be open at once; answer them in any order') and a scope constraint (only within existing approved scope and budget), but never states when to prefer this over settle_questions or raise_work_question, nor what to do if the decision is stale or already answered.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All GenFlick toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources