Skip to main content
Glama

Manage answers

manage_answers
Destructive

Improve, keep, edit and delete answers in the library, and answer the questions only the member can answer. Actions: improve, keep_ai_answers, edit, answer_question, delete, edit_saved, delete_saved, delete_finished. Call with action "help" for each action's fields.

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": {
      "action": "<action>"
    },
    "name": "manage_answers"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
paramsNoFields for the action. Call with action "help" to list each action's fields.
fact_idNoA saved answer's id from get_answers library.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "improve",
      -  "keep_ai_answers",
      -  "edit",
      -  "delete",
      -  "edit_saved",
      -  "delete_saved",
      -  "delete_finished",
      -  "help"
      -]New value: +[
      +  "improve",
      +  "keep_ai_answers",
      +  "edit",
      +  "answer_question",
      +  "delete",
      +  "edit_saved",
      +  "delete_saved",
      +  "delete_finished",
      +  "help"
      +]
  2. Changed2 schema fields changed
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "approve_waiting",
      -  "skip_question",
      -  "rate_question",
      -  "ai_fill",
      -  "ai_fill_always",
      -  "unskip",
      -  "improve",
      -  "keep_ai_answers",
      -  "edit",
      -  "delete",
      -  "edit_saved",
      -  "delete_saved",
      -  "delete_finished",
      -  "help"
      -]New value: +[
      +  "improve",
      +  "keep_ai_answers",
      +  "edit",
      +  "delete",
      +  "edit_saved",
      +  "delete_saved",
      +  "delete_finished",
      +  "help"
      +]
    • removedInput schema / properties / skip_id
      Removed value: -{
      -  "description": "A skipped question's id from get_answers library.",
      -  "pattern": "^skip-[a-f0-9]{16}$",
      -  "type": "string"
      -}
  3. Added

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is supplied structurally. The description adds nothing beyond that – it does not say what deletion destroys, whether deleted answers are recoverable, whether edits are reversible, or whether any action has side effects on the member's profile.

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

Conciseness3/5

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

Two short sentences and front-loaded, which is good, but the entire eight-value action enumeration duplicates the schema enum and burns tokens without adding information. The one genuinely useful pointer (call 'help') is buried at the end.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is an eight-action multiplexed mutation tool with a nested free-form params object and no output schema. The description leaves the per-action contract entirely to a runtime help call, so an agent cannot reliably invoke anything but 'help' or the simplest deletion from this definition alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The action list simply repeats the schema enum verbatim, adding no meaning. The params object is a free-form bag whose per-action fields are documented nowhere except a runtime 'help' call, so an agent cannot construct a valid payload from the definition. fact_id is already fully described in the schema, leaving the description with no compensating value at 67% coverage.

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 concrete verbs (improve, keep, edit, delete, answer) against a named resource (answers in the library), and the read counterpart is inferable from the sibling get_answers. The eight enumerated actions make the tool's scope visible, though what each action actually does to an answer is never explained.

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 a single usage hint ('answer the questions only the member can answer') but no guidance on when to use manage_answers versus get_answers, and no criteria for choosing among the eight actions. Telling the agent to call action='help' defers the decision to runtime rather than stating when each action applies.

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.