Skip to main content
Glama

Lovie Company Formation

Get Approval Session Status

approval_session_get_approval_session_status
Read-only

Read the status of a trusted-device approval session: PENDING, APPROVED, REJECTED or EXPIRED. An approved transfer is sent by Lovie on its own, so this status never asks you to send anything: to learn whether a transfer went through, call get_transfer_draft_outcome with its draft_id instead. Poll once per user prompt, not in a loop; a session expires about 5 minutes after it was opened.

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": {
      "sessionId": "<sessionId>"
    },
    "name": "approval_session_get_approval_session_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionIdYesUUID value wrapper.

Output Schema

NameRequiredDescriptionDefault
statusNo
updatedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / updatedAt / anyOf
      Added value: +[
      +  {
      +    "format": "date-time",
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / updatedAt / format
      Removed value: -"date-time"
    • removedOutput schema / properties / updatedAt / type
      Removed value: -"string"
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/destructive/closed-world annotations, it discloses the two behavioral facts an agent would otherwise get wrong: that approval does not require the agent to send anything, and that sessions self-expire after roughly five minutes. The status enum is also spelled out, so the return vocabulary is known before the call.

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?

Front-loaded with the status list, then the redirect, then the polling/expiry caveats — a sensible ordering with no filler. The clause 'so this status never asks you to send anything' is slightly roundabout phrasing for a useful point.

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?

For a single-parameter status read with an output schema, everything needed to call it correctly is present: what it returns (statuses), how often to call it, how long a session lasts, and which tool answers the adjacent question. No gaps that would cause a misuse.

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 100% and there is only one required parameter, so the schema carries the burden. The description refers to 'a session' but adds no meaning about the sessionId wrapper shape or where a session id comes from — acceptable, but no added value over the schema.

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 ('Read the status of a trusted-device approval session') and enumerates the exact status vocabulary (PENDING, APPROVED, REJECTED, EXPIRED). It also names the sibling it is not for ('to learn whether a transfer went through, call get_transfer_draft_outcome'), so an agent can route without opening either schema.

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 routes the transfer-outcome question to get_transfer_draft_outcome with its draft_id, states the polling cadence ('once per user prompt, not in a loop'), and notes the ~5 minute expiry. This is the when/when-not/alternative triad in compact form.

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.