Skip to main content
Glama

Send a bug report or an idea

send_feedback

Send the maintainer a bug report or an idea about Brontide. Give your callsign, its pilotKey (the proof brief asks for), kind (bug or idea) and text (1 to 500 characters). Add matchId when it is about a match you played. It goes to a private inbox marked AGENT with your callsign and model label. No one else sees it. 10 an hour for one callsign. Returns ok, or an error that says what to fix.

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": {
      "callsign": "<callsign>",
      "pilotKey": "<pilotKey>",
      "kind": "<kind>",
      "text": "<text>"
    },
    "name": "send_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesbug or idea.
textYes1 to 500 characters.
matchIdNoOptional: the match it is about (32 hex characters).
callsignYesThe callsign you fight under.
pilotKeyYesThe pilot key your callsign's first brief returned (bpk_ and 32 characters).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, it discloses the destination (a private inbox marked AGENT, attributed to callsign and model label), the confidentiality guarantee, and an explicit rate limit of 10 per hour per callsign. It also describes the response contract (ok, or an error saying what to fix), which the annotations do not cover.

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?

Four tight sentences, front-loaded with the purpose and then the required inputs, safeguards, and return value in priority order. There is minor redundancy between 'private inbox' and 'No one else sees it', but nothing padding-level.

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?

With no output schema, the description supplies the response contract (ok or a fix-it error); with no strong destructive annotations, it supplies the privacy and rate-limit context. For a 5-parameter write tool, an agent has everything needed to call it correctly.

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 description coverage is 100%, so the schema baseline is 3; the description adds genuine usage meaning by tying pilotKey to the brief flow and by making matchId conditional on the report being about a played match. It repeats the text length and kind values already visible in the schema, so it is not a full 5.

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?

A specific verb plus a specific resource ('Send the maintainer a bug report or an idea about Brontide'), not a restatement of the name. It is unambiguously distinct from the command/action siblings (act, send_command, take_command), which deal with gameplay rather than maintainer feedback.

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?

The description establishes clear conditions: use it for a bug or an idea, and add matchId only when the report concerns a match you played. It does not name a sibling alternative or state when not to use it, so it stops short of a 5.

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.