Skip to main content
Glama
Datris MCP Server

Datris MCP Server

get_approval

Poll a queued approval by approval_id to check whether a mutating tool action is pending, executed, failed, rejected, or expired.

Instructions

Poll one queued approval by the approvalId a mutating tool returned with status pending_approval. Returns its current state: pending (still waiting for a person), executed (approved and performed — resultStatus / resultBody carry the outcome of the original call), failed (approved but the replay failed), rejected, or expired. Poll with wait_seconds between calls, backing off to 30-60s; a decision can take minutes or hours, so after a few polls tell the user you will check back and stop polling unless they ask you to wait.

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": {
      "approval_id": "<approval_id>"
    },
    "name": "get_approval"
  }
}

Input Schema

NameRequiredDescriptionDefault
approval_idYesThe approvalId returned with pending_approval.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does so well: it discloses the complete state machine (pending, executed, failed, rejected, expired), names the fields carrying the replayed outcome (resultStatus/resultBody), and sets timing expectations. It stops short of describing error behavior, e.g. what happens for an unknown or already-collected approvalId.

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?

A single tight paragraph that front-loads the operation, then the return states, then the polling cadence. Every sentence adds information an agent would otherwise have to guess.

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

Completeness5/5

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

There is no output schema, and the description compensates by enumerating every terminal and non-terminal state plus the fields that carry the outcome. Combined with the polling policy, an agent can call this correctly and interpret the result without further context.

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

Parameters4/5

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

Schema coverage is 100% for the single required parameter, so the baseline is 3, but the description adds real meaning by explaining where approval_id originates (a prior pending_approval response) and by naming wait_seconds as the pacing mechanism between calls. The phrasing 'Poll with wait_seconds between calls' is slightly ambiguous about whether that is a parameter or a sibling tool, given the schema lists only approval_id.

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 and resource ('Poll one queued approval by the approvalId') and pins the identifier's provenance to 'a mutating tool returned with status pending_approval', which cleanly separates it from the mutating siblings. The enumerated return states make the scope unambiguous.

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?

Explicitly says how to poll (back off to 30-60s), how long to expect (minutes to hours), and when to stop ('after a few polls tell the user you will check back and stop polling unless they ask you to wait'). This is the when/when-not guidance an agent needs for a long-running polling tool.

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

Deploy Server

Other Tools