Skip to main content
Glama

get_feedback_status

Check the review status of a feedback item previously returned by submit_feedback. Pass the feedback id (starts with fb_). Returns whether the item is pending, approved, or rejected. Does not expose private reviewer or visitor fields. 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": "get_feedback_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesFeedback id returned by submit_feedback, e.g. fb_...

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and does well: it declares the operation read-only, lists the status values, and notes that private reviewer and visitor fields are excluded. It does not cover authentication, rate limits, or error behavior, but the core behavior is transparent.

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?

The description is short and front-loaded, moving from purpose to argument to return values to privacy. A minor amount repeats schema details, such as the fb_ prefix, but no sentence is wasteful.

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 simple one-parameter read-only status lookup, the definition covers purpose, input origin, possible return values, privacy behavior, and safety. No output schema exists, and the description sufficiently explains what the agent gets back.

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 description coverage is 100%, so the id parameter is already documented in the schema. The description adds that it comes from submit_feedback and starts with fb_, but this largely repeats the schema, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: checking the review status of a feedback item. It explicitly ties the item to submit_feedback and names the possible outcomes, so an agent can distinguish it from the sibling tools.

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?

Clearly indicates the tool is for checking status after submit_feedback and implies when to use it. It does not explicitly name alternatives or exclusion cases, but the context is clear enough for correct selection.

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