Feedback & Bug Reports

Overview

The MCP server includes built-in feedback tools for submitting bug reports, feature requests, and general feedback directly from your AI agent session. Feedback is tracked internally by the server maintainers.

Submitting Feedback

Use the submit_feedback tool with the following parameters:

Parameter	Required	Description
type	Yes	"bug", "feature", or "feedback"
title	Yes	Specific, actionable title (10-200 chars)
description	Yes	Detailed description (30-5000 chars)
severity	No	"low", "medium", "high", or "critical" (for bugs)
stepsToReproduce	No	Steps to reproduce the issue (for bugs)
environment	No	Environment info (mode, FIX state, etc.)
contact	No	Optional contact info (email, Slack, etc.) for follow-up

Best Practices

For bug reports:

1. Call check_health first — include the output in the environment field
2. Write a specific title: “MARKET order rejected with INVALID_SYMBOL on EURUSD” not “order broken”
3. Include error codes and messages in the description
4. Add steps to reproduce if possible

For feature requests:

• Describe the use case and why it matters
• Be specific about the desired behavior

Checking Feedback Status

Use get_feedback_status with the feedbackId returned by submit_feedback.

Returns:

• feedbackId: The issue number
• title: Issue title
• status: "open" or "resolved"
• categories: Labels (e.g., “bug”, “feature”)
• createdAt / updatedAt: Timestamps

Tenant isolation: You can only check the status of feedback you submitted in the current session. Attempting to query another user’s feedback ID returns “Feedback not found”.

Rate Limits

Each user can submit up to 10 feedback items per session. This counter resets each session.

If you hit the limit, the tool returns a FEEDBACK_LIMIT_REACHED error with the current count and limit.

Reporter Identification

When feedback is submitted from an authenticated session, the server automatically includes your SenderCompID (trading account identifier) in the report. This allows the team to identify the reporter without requiring extra input.

You can also provide optional contact info (email, Slack handle, etc.) so the team can reach out for details.

What Happens After Submission

1. A ticket is created in the internal feedback tracker
2. The ticket includes your account identifier and optional contact info
3. The team reviews incoming feedback and triages by type and severity
4. Bug fixes and features are tracked until resolved
5. Use get_feedback_status to check if your feedback has been addressed

Availability

Feedback tools are available when enabled via the feedback integration. If not enabled, both tools return a FEEDBACK_NOT_CONFIGURED error.

Feedback tools are available in both authenticated sessions and guest mode.