Skip to main content
Glama

feedback_account

Checks how feedback is published to GitHub—via your gh login or the OS GitHub App—and shows the account and expiry, or signs out the local App authorization.

Instructions

See which way feedback goes to GitHub and as whom, or sign OS's own GitHub authorization out.

"status": gh (the user's gh, logged in), app (OS's GitHub App authorization, made in a feedback_submit dialog when gh could not publish) or none, with the account and when the App authorization runs out. Never shows a token. "sign_out": deletes this machine's App authorization; to revoke it on GitHub as well, give the user the returned revoke_page.

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_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNo"status" (default) or "sign_out"status

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.1

TDQS

A3.8/5.0
Behavior3/5

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

No annotations exist, so the description must carry the behavioral load. It does disclose key traits: 'Never shows a token,' the exact status value set (gh/app/none) with account and App expiry, and precisely what sign_out destroys (this machine's App authorization only, not the GitHub-side grant). What is missing is whether sign_out is reversible/idempotent and what happens when no App authorization exists. With annotations absent, the safety profile is only partly covered, so a 3 fits.

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 definition leads with the two capabilities and then explains each action, so it is front-loaded and free of filler. It is dense but every clause (status values, token non-disclosure, revoke_page follow-up) carries information.

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?

An output schema exists, so return-shape explanation is not required, yet the description still characterizes the status payload (routing source, account, App expiry). Combined with the sign_out effect description, it is effectively complete for a one-parameter auth-inspection tool; only reversibility of sign_out is unaddressed.

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

Parameters4/5

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

Schema coverage is 100% and the schema already documents the action param and its default. The description still adds real meaning beyond the schema by spelling out what each action value returns or destroys, which the schema's one-line enum note does not.

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 states two concrete operations: report how feedback is routed to GitHub (user's gh vs. OS GitHub App) and sign out OS's App authorization. It ties itself to the feedback_submit dialog that created the App authorization, which helps separate it from feedback_submit itself, but it does not explicitly say when to prefer it over the sibling submit/draft 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?

It defines both action values with their operational context: 'status' is the default read of routing/account, and 'sign_out' deletes the machine's App authorization. It also tells the agent the follow-up step (hand the user the returned revoke_page to revoke on GitHub), which is real guidance, though there is no explicit when-not or alternative-tool routing.

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