Skip to main content
Glama

Get intent status

get_intent_status
Read-only

Check an intent's status and optionally wait up to 300 seconds for human approval or denial, enabling agents to pause for human-in-the-loop authorization.

Instructions

Check an intent's status. Pass wait_seconds (up to 300) to block until a human approves or denies it, which is how the agent pauses for human-in-the-loop approval.

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": {
      "intent_id": "<intent_id>"
    },
    "name": "get_intent_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
intent_idYes
wait_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations declare readOnlyHint=true, so safety is covered; the description adds the valuable non-obvious behavior that the call can block for up to 300 seconds awaiting human approval. However, it does not say what happens when the wait elapses without a decision, nor what status values can come back — important for a polling/blocking tool.

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?

Two compact sentences, front-loaded with purpose and followed by the most consequential parameter behavior. No filler or redundancy.

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?

With no output schema, the description should convey what a status check returns; it never names possible statuses or the result when the wait times out. The blocking semantics are covered, but return-value shape is a meaningful gap for an agent deciding how to interpret the response.

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 description coverage is 0%, so the description must carry parameter meaning. It does well for wait_seconds (up to 300, blocks until approve/deny), but intent_id is never explained — its provenance and format are left entirely to the schema's bare 'string' type.

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 and resource: 'Check an intent's status.' An agent can tell this is a status-read tool. It does not explicitly distinguish itself from siblings like submit_purchase_intent, but the resource framing makes the distinction reasonably evident.

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?

Explains the key usage pattern — pass wait_seconds to block for human-in-the-loop approval — which is genuinely actionable. It gives no guidance on when not to block, no mention that an intent must first be created (e.g. via submit_purchase_intent), and no polling advice for the non-blocking case.

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