Skip to main content
Glama

Get approval status

get_approval_status

Read-only. Approval state of one post: required, approvedAt, approverName and changeRequestNote (the approver's requested changes, so you can fix the draft). The agent cannot decide approval; a human does.

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": "get_approval_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe post id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 burden and does meaningful work: it declares 'Read-only', discloses the response fields (important because there is no output schema), and states the authority boundary that the agent cannot decide approval. Missing are edge behaviors such as what is returned when approval is not required or when the post is unknown.

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?

Front-loads the safety profile with 'Read-only.' then delivers the returned fields and the human-approval constraint in two short sentences. Nothing is padded and every clause carries information.

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 read tool with no output schema and no annotations, the description covers safety (read-only), the return payload, and the decision-authority limitation. That is everything an agent needs to invoke it 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?

Only one parameter, and the schema already documents it at 100% coverage ('The post id.'). The description adds no format or sourcing detail beyond that, so the schema is doing the work here and baseline 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 ('Approval state of one post') and enumerates exactly what comes back: required, approvedAt, approverName, changeRequestNote. The 'one post' scope plus the id parameter make it clearly distinct from list-scoped siblings like list_pending_approvals, though no sibling is named.

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?

Usage is only implied via the parenthetical 'so you can fix the draft', which hints at the edit-after-rejection workflow. There is no explicit statement of when to call this versus list_pending_approvals or get_post, and no exclusion or prerequisite guidance beyond the note that approval is a human decision.

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.

Resources