Skip to main content
Glama

workbuddy_answer_permission

Submit a user-confirmed answer or approval decision for a WorkBuddy request after displaying the exact prompt, preventing automatic approval of destructive or external actions.

Instructions

Answer a WorkBuddy AskQuestion or approval request. Call only after showing the exact request to the user and receiving their decision; never auto-approve destructive or external actions.

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": {
      "requestId": "<requestId>",
      "answers": "<answers>"
    },
    "name": "workbuddy_answer_permission"
  }
}

Input Schema

NameRequiredDescriptionDefault
answersYes
requestIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/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. It does disclose important safety behavior: user confirmation must precede the call, and destructive or external actions must never be auto-approved. It does not state what happens on success, whether the pending request is consumed, or how an invalid or already-answered requestId fails, which is a meaningful gap for a tool that resolves requests.

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 tight clauses, with the core action first and the safety precondition immediately after. Every sentence carries an instruction the agent must follow, and there is no padding.

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 definition is complete on the safety and sequencing dimension, which is the riskiest part of this tool. It is incomplete on the mechanics: with no annotations, no output schema, and undocumented nested parameters, the agent still does not know the answer payload shape or what the call returns. Adequate for safe invocation, not fully sufficient for correct invocation.

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?

Schema description coverage is 0% across two required parameters, so the description must compensate and largely does not. It only obliquely implies requestId through 'the exact request.' The answers parameter is a nested map whose values may be a string or an array of strings, and the description gives no indication of the expected key/value shape or how multi-part questions are answered.

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 uses a specific verb plus a specific resource: 'Answer a WorkBuddy AskQuestion or approval request.' That scopes the tool to responding to pending requests rather than initiating dialogue, which is enough to separate it from message-sending siblings like workbuddy_send_message. It stops short of naming an explicit alternative, so it is not a 5.

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?

The description gives a clear precondition for invocation: call only after showing the exact request to the user and receiving their decision. It also adds a negative rule: never auto-approve destructive or external actions. What is missing is a pointer to how the agent should retrieve the request in the first place, such as which sibling produces the AskQuestion payload.

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