Skip to main content
Glama

Send feedback

feedback

Sends a note to the Moose Tracker team about a bug, a confusing tool, or a missing feature. Up to 20000 characters per call; longer reports can be split into parts. Notes are kept 1 year; include what happened, the call and its reply. Schema a964948f.

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": {
      "type": "<type>",
      "message": "<message>"
    },
    "name": "feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
mtlNoOptional: the song or sound involved, only if relevant
refNoOptional label shared by every part of one long report; parts with the same ref count as one submission
partNoWhich part this is (1 based)
typeYes
partsNoHow many parts in all
messageYesWhat happened or what is needed; no personal details. Up to 20000 characters; longer reports go in parts (ref, part, parts).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 826121bd"New value: +"Schema a964948f"
  2. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 2d544474"New value: +"Schema 826121bd"
  3. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 0781812e"New value: +"Schema 2d544474"
  4. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 0d11f08d"New value: +"Schema 0781812e"
  5. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 2d7abb8b"New value: +"Schema 0d11f08d"
  6. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema ff675289"New value: +"Schema 2d7abb8b"
  7. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 2a55f659"New value: +"Schema ff675289"
  8. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 71227a86"New value: +"Schema 2a55f659"
  9. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 64bfe66c"New value: +"Schema 71227a86"
  10. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema eb59845f"New value: +"Schema 64bfe66c"
  11. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 3b8fe45c"New value: +"Schema eb59845f"
  12. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 9b20e675"New value: +"Schema 3b8fe45c"
  13. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 415a8741"New value: +"Schema 9b20e675"
  14. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema d568427c"New value: +"Schema 415a8741"
  15. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 90ddc268"New value: +"Schema d568427c"
  16. Changed1 schema field changed
    • addedInput schema / description
      Added value: +"Schema 90ddc268"
  17. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare write/non-destructive/openWorld=false hints. The description adds real behavioral context: a 20000-character ceiling per call, the ability to split long reports into parts, a one-year retention policy, and guidance to include what happened plus the call and its reply. It does not say whether a submission returns an ID or confirmation, which would be the remaining gap.

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, then limits, then retention, then reporting guidance. The trailing 'Schema a964948f.' is machine noise that does not earn its place and is the only real waste.

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?

With six parameters, no output schema, and purely write-side annotations, the description covers the essentials an agent needs: size ceiling, multi-part mechanism, retention, and what content to include. Only the post-submission result (confirmation, identifier, or error behavior) is left unstated.

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 83%, so the schema already explains mtl, ref, part, parts, and message. The description restates the character limit and the part-splitting workflow but adds no new meaning about how ref, part, and parts interact beyond what the parameter descriptions already say. 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?

States a specific verb and destination ('Sends a note to the Moose Tracker team') plus the three accepted report categories (bug, confusing tool, missing feature). This clearly separates it from siblings like describe, render, or research_composition, which serve the tool-user rather than the tool maintainers.

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 makes the intended situation clear: report a bug, a confusing tool, or a missing feature. There are no alternative feedback channels named and no exclusions such as 'do not use for feature questions about X', but for a lone channel this is unambiguous enough to act on.

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