Skip to main content
Glama

Get the approval state of a post

get_approval
Read-onlyIdempotent

The latest approval request for a post: decision (PENDING, APPROVED or CHANGES_REQUESTED; the reviewer page offers only those two, so REJECTED never appears), the reviewer, when it was opened and decided, the reviewer's comment, and the team's internal notes on the post (add_post_note; the reviewer never sees them).

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": {
      "workspace_id": "<workspace_id>",
      "post_id": "<post_id>"
    },
    "name": "get_approval"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYes
workspace_idYesWorkspace id from list_workspaces

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, so the bar is lower, and the description still adds real domain semantics beyond them: it returns only the LATEST request (not history), enumerates the decision values, explains that REJECTED never appears because the reviewer page offers only two options, and discloses that internal notes are invisible to the reviewer. It does not cover behavior on a post with no approval request at all.

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?

A single sentence, front-loaded with the resource, and every clause carries information. The nested parentheticals make it dense to parse, but nothing is redundant.

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?

With no output schema, the description does the heavy lifting on return values and does it well, covering decision, reviewer, timestamps, comment and internal notes. Gaps remain around the no-approval-exists case and the undocumented post_id, but the core shape is complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%: workspace_id is documented in the schema, but post_id carries no description anywhere. The description says only 'for a post', which restates the obvious without adding format, source, or how to obtain a post_id, so it does not compensate for the coverage gap.

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?

The description names the resource (the latest approval request for a post) and enumerates its payload, making the retrieval purpose unambiguous even though it is phrased as a noun clause rather than a verb. It is clearly distinct from siblings like request_approval, revoke_approval and list_reviews, though it never explicitly contrasts itself with them.

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

Usage Guidelines2/5

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

There is no statement of when to reach for this tool versus request_approval, revoke_approval, list_reviews or get_post; the agent must infer that it is the read counterpart to the approval mutation tools. The mention of add_post_note is a cross-reference to where notes are written, not usage guidance for this tool.

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