Skip to main content
Glama

Freigabe entscheiden

approval_decide
Destructive

Gibt eine wartende Freigabe frei oder lehnt sie ab. 'approve' setzt voraus, dass diese OAuth-Verbindung die zusätzlich erteilte Berechtigung approval:self_approve trägt. Fehlt diese Berechtigung, öffnet der Mensch den zurückgegebenen approvalUrl und entscheidet im angemeldeten Portal. approval:decide bleibt ebenfalls erforderlich. Bei Freigabe durch den Agenten geht der Brief nach 10 Minuten raus und kann bis dahin mit order_cancel gestoppt werden. EN: Approves or rejects a pending approval. 'approve' requires that this OAuth connection carries the separately granted approval:self_approve scope. When that scope is absent, the human opens the returned approvalUrl and decides in the signed-in portal. approval:decide is also required. An agent approval dispatches after 10 minutes and can be stopped with order_cancel until then.

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": {
      "approvalId": "<approvalId>",
      "decision": "<decision>"
    },
    "name": "approval_decide"
  }
}

Input Schema

NameRequiredDescriptionDefault
commentNo
decisionYes
reasoningNo
approvalIdYes
clientOrderIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / user_saw_preview
      Removed value: -{
      -  "description": "Bestaetigung, dass du dem Menschen die Vorschau-PDF, den genauen Preis und die Versandart gezeigt und seine Zustimmung eingeholt hast. Fuer eine Freigabe erforderlich. EN: Confirmation that you showed the human the preview PDF, the exact price and the delivery type and obtained consent. Required to approve.",
      -  "type": "boolean"
      -}
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only say destructive/openWorld; the description adds the details that actually matter: a two-scope authorization requirement (approval:self_approve plus approval:decide), a returned approvalUrl fallback, and a 10-minute delay before dispatch during which order_cancel can undo the decision. That is real behavioral disclosure the structured fields do not carry.

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?

The content is well front-loaded (decision semantics and scope precondition first, timing consequences last), but the entire text is duplicated verbatim in German and English, roughly doubling length for the same information.

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 mutation with no output schema, the description covers authorization, the human fallback (returned approvalUrl), and the post-decision timing/undo window, which is the material an agent needs before calling. The remaining gap is per-parameter meaning, especially comment and reasoning, which matters since they likely feed the approver.

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%, so the description must explain the five parameters. It only clarifies the meaning of the 'approve' value of decision; approvalId, comment (1000-char cap), reasoning, and clientOrderId are left entirely undefined in both schema and description.

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?

States a specific verb pair and resource: releases or rejects a waiting approval. It also distinguishes the two paths (agent approval vs. human decision via returned approvalUrl), which is the key axis separating it from approval_decide_app and approval_submit without opening their schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use conditions: 'approve' only works if the OAuth connection carries approval:self_approve; if absent, the human must use the returned approvalUrl instead. It also names order_cancel as the way to stop a dispatched approval within the 10-minute window, so the agent knows both the precondition and the undo path.

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.