Skip to main content
Glama

open_approvals

Read-only

View and act on your pending ServiceNow approvals directly in chat with Approve and Reject buttons, or receive the list as JSON when interactive apps aren't supported.

Instructions

Show the current user's pending approvals as an interactive list with Approve and Reject buttons inside the chat. Hosts without MCP Apps get the list as JSON.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "open_approvals"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax approvals to show (default 20, max 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, but the description adds genuinely new behavior: output is rendered as an interactive UI with Approve and Reject controls inside the chat, and degrades to plain JSON on hosts lacking MCP Apps. That host-capability caveat is the kind of context an agent cannot get from the schema or annotations. A small gap remains: it does not clarify that the Approve/Reject buttons are client-side actions rather than mutations performed by this call, which could otherwise seem at odds with readOnlyHint=true.

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 sentences, zero filler, and the primary purpose is front-loaded before the host-compatibility caveat. Every clause carries distinct 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 simple zero-required-parameter read tool with a fully documented schema and safety annotations, the description covers purpose and the notable rendering/fallback behavior. The only omission is guidance on choosing this over the similarly named approval-listing siblings, which matters given the crowded sibling set but is not strictly required to invoke the tool correctly.

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?

There is a single optional parameter (limit) and schema description coverage is 100%, with the default (20) and max (50) already documented in the schema. The description adds nothing about the parameter, so the baseline of 3 applies.

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 scoped resource ("Show the current user's pending approvals") and adds the rendering mode (interactive list with Approve/Reject buttons in chat). It implicitly distinguishes itself from similarly named siblings like get_my_approvals and list_approvals through the in-chat interactive presentation, but never names them, so the differentiation is inferred rather than explicit.

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?

The description never says when to prefer this over get_my_approvals or list_approvals, and gives no exclusions. The only conditional guidance is environmental ("Hosts without MCP Apps get the list as JSON"), which is a runtime fallback rather than a task-selection rule, so usage is only implied by the mention of interactive buttons.

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