Skip to main content
Glama

Proposal status

zarok_get_proposal_status
Read-onlyIdempotent

Returns whether a proposal made by this connection was approved, dismissed or is still pending. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe proposal id returned by zarok_propose_changes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / id / description
      Added value: +"The proposal id returned by zarok_propose_changes"
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the trailing 'Read-only.' adds nothing. The real value is disclosing the three possible return states, which matters because there is no output schema and the agent otherwise wouldn't know what values to expect back.

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 short sentences, outcome information front-loaded with no wasted preamble. The redundant 'Read-only.' is the only slack, and it is a phrase, not a paragraph.

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?

A one-parameter read tool with full schema coverage and no output schema; the description covers the essential unknown (what the returned status values are). It stops short of saying whether a pending status is stable or how long approval takes, but nothing needed to invoke it correctly is missing.

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 description already explains the id comes from zarok_propose_changes. The description adds no further meaning about the parameter, so the 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 and resource (returns proposal status) and enumerates the possible outcomes (approved, dismissed, pending), which distinguishes it from the sibling zarok_propose_changes that creates proposals. It doesn't name the sibling explicitly, but the resource is unambiguous.

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 implied — you call this after zarok_propose_changes to check the outcome — but the description never says when to use it versus alternatives or how polling should be done. The schema's id description carries the only explicit linkage back to zarok_propose_changes.

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