Skip to main content
Glama

File engine feedback

feedback

File bugs, surprises, or workarounds from a session as GitHub issues on the aidemo engine repo, with environment and recent log context attached automatically.

Instructions

File a bug, surprise, or workaround you hit this session as a GitHub issue on the aidemo engine repo (github.com/tandryukha/aidemo) — the in-band equivalent of aidemo feedback on the CLI. Environment (engine version, OS, node, ffmpeg) and a recent-log tail from dir are auto-attached, same as the CLI. Uses gh issue create when available; falls back to a local docs/feedback-*.md plus a prefilled github.com New Issue URL when gh is missing or offline — no other network call. Call this whenever something felt broken, surprising, or needed a workaround; skip it if the session was clean. Set dryRun to preview the assembled title/body without filing anything.

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": {
      "title": "<title>",
      "body": "<body>"
    },
    "name": "feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
dirNodemo dir to pull storyboard/log context from (recommended)
webNoprefer a prefilled browser New Issue URL over filing via gh
bodyYeswhat happened / suggestion — the actual finding (broken selector, bad timing, confusing behavior, an idea). Environment/log context is appended automatically; don't duplicate it here.
titleYesshort issue title
dryRunNoassemble the title/body but don't file anything — preview only

Output Schema

NameRequiredDescriptionDefault
urlNo
bodyYes
filedYes
titleYes
messageYes
localPathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.20.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observedv0.9.0

TDQS

A4.6/5.0
Behavior5/5

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

No annotations are supplied, so the description carries the full burden and does so: it discloses that environment data and a recent log tail are auto-attached, that it shells out to `gh issue create`, that it degrades to a local docs/feedback-*.md plus prefilled New Issue URL when gh is unavailable, and that it makes no other network call. Side effects (creating a public GitHub issue, writing a local file) and the dryRun escape hatch are all surfaced.

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?

Front-loaded with purpose and tightly written, with no filler sentences. It is a single dense run of em-dash clauses, though, which makes the fallback and dryRun details harder to scan than separate lines would 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?

An output schema exists, so return values need no explanation. For a mutating tool with external side effects, the description still covers trigger conditions, required inputs, auto-attached data, the offline fallback, and the preview mode — everything an agent needs to call it safely.

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 all five parameters are already documented in the schema, including dryRun, web, and dir semantics. The description restates dryRun preview and the dir-based log context rather than adding meaning beyond it, so the baseline of 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?

States a specific verb and resource: file a bug/surprise/workaround as a GitHub issue on the named repo (github.com/tandryukha/aidemo), and anchors it to the CLI equivalent `aidemo feedback`. No sibling tool in the list files feedback, so the boundary 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 Guidelines5/5

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

Gives an explicit trigger ("whenever something felt broken, surprising, or needed a workaround") and an explicit exclusion ("skip it if the session was clean"). It also names the branch conditions between filing paths (gh available vs. missing/offline) and the dryRun preview mode.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.