Skip to main content
Glama

feedback_list

List feedback filed from OS newest first with kind, title, status, GitHub number, and URL; settle open rows by checking expired drafts or unknown sends against GitHub without resending.

Instructions

List the feedback filed from OS, newest first: kind, title, status, GitHub number and URL.

Summary rows only (no text). Reading also settles open rows: an expired draft, or a send whose result was unknown (checked against GitHub, never resent).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "feedback_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many rows, 1 to 100 (default 20)
statusNoOnly this status (draft, sending, sent, unknown, failed, handed_off, refused, expired); empty: all

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.1

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose a genuinely important trait: this read has a write side effect, settling expired drafts and rows whose send result was unknown by checking GitHub and explicitly never resending. That is exactly the kind of non-obvious behavior an agent needs. It still omits pagination/limit interaction and any authorization context.

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?

Three short sentences, each earning its place: the first gives the resource and shape, the second bounds the payload to summaries, the third discloses the side effect. Front-loaded and free of filler.

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?

For a 2-parameter read tool with a full output schema and 100% schema coverage, the key gaps are covered, especially the state-settling side effect. Only secondary details such as pagination and permission requirements are absent.

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%, with both limit and status fully documented including the status enum values, so the baseline is 3. The description adds ordering ('newest first') and row scope ('summary rows only, no text') but nothing further about how limit or status behave.

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 opens with a specific verb and resource ('List the feedback filed from OS'), and adds ordering ('newest first') plus the returned fields (kind, title, status, GitHub number and URL). It is clearly a listing tool, though it never names the sibling submit/draft tools to contrast read-listing against filing.

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 rather than stated: 'Reading also settles open rows' hints at when to call it (to reconcile draft/unknown rows), but there is no explicit when-to-use, when-not-to-use, or named alternative among feedback_draft/feedback_submit/feedback_account.

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