Skip to main content
Glama

feedback_submit

Publish a confirmed feedback draft by handling user approval, GitHub authorization, and posting; returns the published URL or a prefilled GitHub link when direct submission isn't possible.

Instructions

Publish a draft from feedback_draft, once the user confirms it in the client's own dialog.

The dialog shows where it goes, the title, the content hash and the stored text; the user's Accept there publishes at once, Decline sends nothing and keeps the draft. When neither the user's gh nor an earlier authorization can publish, a second dialog has the user authorize OS's GitHub App on github.com (a code to enter); the post then goes out. "authorizing": the user has not finished yet; call again when they say so (no new question, same code). Without a dialog (not supported, cancelled, unanswered for five minutes) nothing is sent and you get a prefilled GitHub link instead: give it to the user, who submits on GitHub. After publishing, tell the user the URL.

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": {
      "draft_id": "<draft_id>"
    },
    "name": "feedback_submit"
  }
}

Input Schema

NameRequiredDescriptionDefault
draft_idYesThe draft_id returned by feedback_draft

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.1

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so: it explains the two dialogs, the GitHub App authorization flow with a code, the five-minute timeout, that nothing is sent when the dialog fails, and that a prefilled GitHub link is returned for manual submission. It also tells the agent to report the post URL to the user afterwards.

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?

Purpose is front-loaded and nearly every sentence carries behavioral information, but the middle sentences are long and heavily parenthesized, which makes the states harder to scan than they could be.

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 one-parameter mutation with an output schema, the description covers the full state machine: confirmation, authorization retry, timeout fallback, and the follow-up action after success. Nothing an agent needs in order to call 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 single parameter is fully documented there, including that it is the draft_id returned by feedback_draft. The description adds no syntax, format, or validity detail beyond the schema, so the baseline 3 applies.

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?

The opening sentence gives a specific verb and resource ('Publish a draft from feedback_draft') and ties it directly to the sibling that creates the draft, so an agent can tell it apart from feedback_draft without opening either schema.

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

Usage Guidelines5/5

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

It states the triggering condition (the user confirms in the client's own dialog), the when-not path (no dialog, cancelled, unanswered for five minutes), and the retry condition ('authorizing': call again when they say so, same code, no new question). Alternatives and exclusions are explicit.

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