Skip to main content
Glama

trw_submit_feedback

Send categorized feedback, bug reports, or feature requests to the TRW maintainer. Automatically attaches environment details for context.

Instructions

Submit a memo to the TRW maintainer (PRD-CORE-182).

Use when:

  • You found a bug, installation problem, or rough edge worth flagging.

  • You want to send a feature request or piece of feedback that deserves a real reply instead of disappearing into a personal log.

  • You want the maintainer to see exactly which trw-mcp / Python / OS you are on without retyping it — environment metadata is attached automatically.

Input:

  • category: one of bugfix, installation, feedback, feature_request, question, other.

  • subject: short headline (1-200 chars, no newlines).

  • message: full memo body (10-10000 chars).

  • contact_email: optional reply-to address; defaults to no reply-to.

  • metadata: optional extra key/value pairs (16 keys max, 200 char values max). Merged on top of the auto-attached environment dict.

Output: dict with success, submission_id (when 200), error (when non-200), status_code (HTTP status or 0 on validation/transport error), and metadata_attached (the dict actually sent so you can audit it locally).

Never raises — transport and validation failures are reported in the error field.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYes
subjectYes
categoryYes
metadataNo
contact_emailNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations, the description discloses key behaviors: automatic metadata attachment, error handling that never raises, and output format. This adds substantial value beyond the schema.

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 description is well-structured with sections, front-loads purpose, and each sentence adds value. Slightly verbose but still efficient.

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?

The description covers input, output fields, error handling, and automatic metadata. With an output schema present, it is complete for the tool's complexity.

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

Parameters5/5

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

Despite 0% schema description coverage, the description explains each parameter in detail: category options, subject constraints, message length, optional contact_email, and metadata limits. Fully compensates for missing schema descriptions.

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?

The description clearly states the tool submits a memo to the TRW maintainer and lists specific use cases (bug, installation problem, feature request, etc.). It distinguishes itself from the sibling tools, none of which are for feedback submission.

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 includes a 'Use when:' section with explicit scenarios, providing clear context. It does not list exclusions or alternatives, but the positive guidance is sufficient.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wallter/trw-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server