Skip to main content
Glama

Reply about a problem

gap_reply

ANSWER ON YOUR TICKET — and, when it is pending, CLOSE IT OR SEND IT BACK. verdict: "fixed" means you ran the verify line from gap_check and it works: the ticket closes stamped as confirmed by the reporter. verdict: "still_broken" means you ran it and it does not: the ticket goes straight back onto the queue, red, with your sentence as the reason it bounced — no re-filing, and that line is the most useful one on the whole list, because it says a fix we believed in did not hold. A verdict only applies to a pending ticket: nothing else is waiting on your answer, and on an open or closed one your message lands in the thread for a person to read instead. Leave verdict off to just add to the ticket. still_broken needs the sentence — say WHAT is still wrong, or it goes back to a queue with nothing to act on. Same rule as filing: describe the capability, never the person, and never paste your human's brief. Only the reporter who created this ticket may give a verdict; any signed-in reporter on the ticket may add a sentence. A RECEIPT (pr_…) can stand in for the id when the filing was anonymous: it adds a sentence to the filing it belongs to, but it never carries a verdict — that belongs to the signed-in reporter who created the ticket. Tickets are private to their reporters, so a ticket id alone no longer reads a thread. The public roadmap shows only worked tickets with identifiers removed.

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": "gap_reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNothe ticket id, `pg_…`. Give this or `receipt`.
messageNowhat you want to say — for `still_broken`, what is still wrong when you run the test
receiptNothe `pr_…` receipt report_gap returned with the filing. Gives a sentence, never a verdict.
verdictNoonly on a `pending` ticket: `fixed` closes it, `still_broken` returns it to the queue. Leave it off to add to the thread without deciding. The signed-in originator only; never with a receipt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"the ticket id, `pg_…`"New value: +"the ticket id, `pg_…`. Give this or `receipt`."
    • addedInput schema / properties / receipt
      Added value: +{
      +  "description": "the `pr_…` receipt report_gap returned with the filing. Gives a sentence, never a verdict.",
      +  "type": "string"
      +}
    • changedInput schema / properties / verdict / description
      Previous value: -"only on a `pending` ticket: `fixed` closes it, `still_broken` returns it to the queue. Leave it off to add to the thread without deciding."New value: +"only on a `pending` ticket: `fixed` closes it, `still_broken` returns it to the queue. Leave it off to add to the thread without deciding. The signed-in originator only; never with a receipt."
    • changedInput schema / required
      Previous value: -[
      -  "id"
      -]New value: +[]
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only flag this as a non-read, non-destructive, non-idempotent open-world write; the description goes far beyond by disclosing state transitions (ticket stamped confirmed vs. bounced back red with the sentence as reason), that `still_broken` without a sentence leaves a queue with nothing to act on, and the rule that tickets are private to their reporters. It also explains that a receipt adds a sentence but can never carry a verdict. Nothing here contradicts readOnlyHint=false or destructiveHint=false.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and the highest-value rule (verdict semantics) are front-loaded, and nearly every sentence carries a distinct policy. However, the text is a dense run-on of all-caps and em-dash clauses with several rules chained in single sentences, which makes it harder to scan than it needs to be for a four-parameter tool.

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 four-parameter, non-destructive write with no output schema, the description covers permissions, side effects, identifier alternatives, privacy, and content constraints (describe capability, never the person, never paste the brief). It stops short of describing what the tool returns on success (ticket state, thread entry), which would be the last piece an agent needs to confirm the action landed.

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%, so the baseline is 3, but the description adds real meaning beyond the schema: `receipt` and `id` are mutually substitutable identifiers with different powers, a ticket id alone no longer reads a thread, and `verdict` is valid only on pending tickets and never with a receipt. The only gap is that it doesn't clarify what `message` alone does on a non-pending ticket beyond landing in the thread.

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?

Opens with a concrete verb+resource ("ANSWER ON YOUR TICKET") and immediately scopes it against the related verbs in the family: `gap_check` produces the `verify` line, `report_gap` files, this tool answers. An agent can separate gap_reply from report_gap and gap_check without opening any 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?

Explicit branching guidance: a verdict applies only to a `pending` ticket, `fixed` closes it, `still_broken` returns it to the queue, and leaving `verdict` off simply appends to the thread on open/closed tickets. It also states the permission split (only the originating reporter may give a verdict; any signed-in reporter may add a sentence), which is exactly the when/when-not detail needed.

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