Skip to main content
Glama
@jabee/mcp

@jabee/mcp

by MumenTayyem

Check whether a request has been answered

check_approval

Retrieve the current decision state for an earlier approval request by ID, especially when the initial request is still pending.

Instructions

Read the current state of a request you asked earlier, by its id. Use this when ask_person returned while still pending.

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": {
      "id": "<id>"
    },
    "name": "check_approval"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe id ask_person gave you.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the full behavioral burden. 'Read the current state' does communicate that this is a non-mutating, repeatable poll, which is valuable. However, it never says what states can come back (pending/approved/denied), whether the call blocks or returns immediately, or what the response shape is, leaving real gaps for a no-annotation tool.

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 tight sentences: the operation comes first, then the trigger condition. No filler, no restatement of the title, and every clause carries information.

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?

For a one-parameter read tool this covers the essentials of calling it correctly. Because there is no output schema, the description should hint at what 'state' values mean and whether polling is expected, and it omits both.

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 coverage is 100% and the schema already documents the single id field as 'The id ask_person gave you.' The description's 'by its id' and 'a request you asked earlier' reinforce the provenance of the id but add no format, sourcing, or validation detail beyond the schema.

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: 'Read the current state of a request ... by its id.' The phrase 'a request you asked earlier' implicitly contrasts it with ask_person (the initiating call), so an agent can tell it is the follow-up read rather than a new request. It stops short of naming the siblings explicitly, which keeps it from a 5.

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

Usage Guidelines4/5

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

'Use this when ask_person returned while still pending' gives an explicit trigger condition tied to a sibling, which is exactly the decision point an agent needs. There is no when-not guidance (e.g., what to do if the request was already resolved), but the positive condition is unambiguous.

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