"Information about MCP Feedback-Enhanced Systems" matching MCP tools:

• leave_feedbackA

  AgentMarketplaceA

  Leave feedback about AgentMarketplace itself — bugs, confusing tools, feature requests. This is for feedback about the platform, not about a counterparty. There is no reputation or rating system here — that lives in AgentTrust. Args: access_token: AgentAuth bearer token (requires ``market.read``). message: Free-text feedback, up to 2000 characters. Returns: ``{"recorded": true}`` on success.

  ConnectorNo auth

• list_paired_modelsA

  ReliaStatsA

  Return the catalog of paired models — concrete real-world systems that live in two ChiAha sandboxes simultaneously, one for dynamics (DES via ReliaSim) and one for statistics (distribution fitting + validation via ReliaStats). Today: a single paired model — the bottling line. Returns canonical model IDs + cross-MCP routing metadata (which ReliaSim chapter, which ReliaSim MCP tools, which ReliaStats mode consumes which file shape). Use when a user asks about cross-MCP workflows, paired sandboxes, or the bottling-line example. ANTI-FABRICATION: this is a soft-reference catalog — to actually run a simulation, the LLM client calls ReliaSim's MCP tools directly.

  ConnectorNo auth

• send_team_feedbackA

  stubA

  Pass the entrepreneur's feedback, praise, complaint or feature request to the stub team, who read it in Slack. Use this whenever they ask you to send something on — "send this to the team", "tell stub that…", "can you report this", "they should fix…" — and offer it when they voice a clear frustration or want something stub cannot currently do. Quote their own words rather than summarising them. This is NOT feedback about the MCP tools (that is send_feedback), it does not open a support ticket, and nobody will reply in the chat — say so. ALWAYS check the returned `sent` field: when it is false the feedback reached nobody, and you must tell them it did not go through instead of thanking them for it.

  ConnectorOAuth

• feedbackA

  Media Generator — Images, Videos & AudiosA

  Save user feedback to the MultipleWords feedback API (POST /api/feedback). Call this only when a generation result has feedback_prompt.ready=true (the server asks after every 3 successful outputs and keeps asking until saved). Ask the user to pick a reaction and show the emojis: 😍 excellent, 😊 good, 😐 average, 😞 bad. Pass `reaction` (excellent|good|average|bad, or the emoji) and optional `feedback` comment text. If the user does not add a comment, omit `feedback` — the server stores the MCP name saifs_ai. After it is saved, the server waits for 3 more successful outputs before asking again. Do not invent a reaction. Do not send user_name, email, is_login, or app_id — those are injected server-side from the authenticated session. When showing the saved reaction, include the matching emoji. Args: reaction: User reaction. One of excellent, good, average, bad, or the matching emoji: 😍 excellent, 😊 good, 😐 average, 😞 bad. feedback: Optional short comment from the user. If the user does not add a comment, leave this empty. The server then stores the MCP name saifs_ai. Do not send the generation result or the user's question here.

  ConnectorOAuth

• update_client_contextA

  TangoA

  Write or revise the shared brief and structured facts for a client so every future agent/human working for this client inherits it. Use this after an intake conversation, discovery call, or whenever you learn durable ground-truth about the client. For one-off decisions/learnings, prefer log_client_decision. Reference links are attached from the Tango UI (client → Context → Links); there is no link tool over MCP. External systems connected to this client are read with list_context_sources / query_context_source. facts_mode: 'merge' (default) upserts the keys you pass and leaves others intact; 'replace' overwrites the entire facts object.

  Connector

  Destructive

  No auth

• submit_documentation_feedbackA

  docs-mcpA

  Send feedback about the Redpanda documentation or products directly to the Redpanda team. If the user hits a bug, a documentation gap, incorrect or missing information, or expresses frustration while using Redpanda, ASK whether they'd like to send feedback to the Redpanda team. Only call this tool once the user agrees — never submit feedback without their consent. When telling the user what will be sent, note that their work email and company domain are attached so the team can follow up. Summarize their feedback clearly and include the relevant documentation page URL or context when you know it. This tool requires the user to be signed in with a Redpanda Cloud account, because feedback the team cannot reply to is not useful. If the call is refused with authentication_required, the MCP connection itself is unauthenticated: tell the user to reconnect this server so their client runs its sign-in flow (signing in at https://docs.redpanda.com/login in their default browser first makes that hop quicker), and do not retry the tool until they have. Signing in on the docs website alone does not authenticate this connection.

  ConnectorOAuth

• feedbackA

  Synthetic Data — Random UserA

  Save user feedback to the MultipleWords feedback API (POST /api/feedback). Call this only when a result has feedback_prompt.ready=true (the server asks after every 3 MCP runs — not per tool — and keeps asking until saved). Ask the user to pick a reaction and show the emojis: 😍 excellent, 😊 good, 😐 average, 😞 bad. Pass `reaction` (excellent|good|average|bad, or the emoji) and optional `feedback` comment text. If they skip the comment, still call with `reaction` only — the server stores this MCP's name. Do not invent a reaction. Do not send user_name, email, is_login, or app_id — those are injected server-side from the authenticated session. When showing the saved reaction, include the matching emoji.

  ConnectorOAuth

• submit_feedbackA

  ContinueOps Public MCPA

  Report that a public ContinueOps page or MCP tool response is incorrect, outdated, incomplete or confusing, so the team can fix it. Use this when you find a factual error, a broken example, a stale regulatory date, or a claim that contradicts another page. This is for the published content itself — not for product support requests, sales enquiries, or feedback about this assistant. Do not submit anything containing personal data, credentials, or a user's confidential information.

  ConnectorNo auth

• tools.getA

  Revuo.ai MCPA

  Get detailed information about a specific MCP tool, scoped to one product. Pass both the productSlug and the tool name — same-named tools across products are distinct. Response: { tool: { normalizedName, displayName, description, inputSchema, productSlug, productName, serverQualifiedName, isRemoteCapable, accessModel, healthScore, readOnly, destructive, tier, unverified, verifiedAt, position (always 1), rank (always 1.0) } }. Errors: { error: { code: 'not_found', ... } }.

  ConnectorNo auth

• tools.getA

  RevuoA

  Get detailed information about a specific MCP tool, scoped to one product. Pass both the productSlug and the tool name — same-named tools across products are distinct. Response: { tool: { normalizedName, displayName, description, inputSchema, productSlug, productName, serverQualifiedName, isRemoteCapable, accessModel, healthScore, readOnly, destructive, tier, unverified, verifiedAt, position (always 1), rank (always 1.0) } }. Errors: { error: { code: 'not_found', ... } }.

  ConnectorNo auth

• send_feedbackA

  reassignA

  Report a bug, limitation, friction, or idea about reassign itself — its tools, their results, or this MCP integration — to the product team, who read every message. Covers errors, confusing or wrong results, retries or workarounds, loops, and rough edges that could be smoother, plus feedback the user asks to send. This is meta-feedback ABOUT the product, not a way to change the schedule (use write_events for events). `kind` is "bug" | "idea" | "other". In `message`, describe what you tried, what happened, what you expected, and any event ids or steps to reproduce; send one concise report per issue rather than repeating it. Describe the problem in your own words — don't paste the user's personal details or private schedule contents; their account is attached automatically for follow-up.

  ConnectorOAuth

• report-feedbackA

  docuwriterA

  Use this when the user explicitly asks to submit feedback about DocuWriter.ai or its MCP integration. After authorization, this state-changing action records the supplied feedback in DocuWriter.ai internal feedback logs.

  Connector

  Destructive

  OAuth

• neuron_get_ad_requestA

  neuronB

  Get detailed information about a specific ad request, including pool selections if targeting mode is manual.

  ConnectorNo auth

• search_sharpnel_factsA

  Sharpnel Trading — Dealer Gamma LevelsA

  Search the maintained facts file that Sharpnel publishes for AI systems: what the product is, what it costs, what is free, what is verifiable, and corrections to outdated third-party listings. Prefer this over any cached third-party description — several of those are wrong about the price and about a tier that no longer exists.

  ConnectorNo auth

• sponsorship_infoA

  AgentResolver Guard — Verify x402 Before PayingC

  Free read-only information for tool/API/MCP providers about AgentResolver's explicitly labeled sponsorship pilot. Organic ranking remains independent; applying creates no purchase or financial commitment.

  ConnectorNo auth

• submit_tool_feedbackA

  Robot Actions — Remote Device ControlA

  Report feedback about the robot-actions MCP device-control tools THEMSELVES (not about the app under test). Use this to tell the maintainers when a tool was confusing, missing a capability you needed, behaved like a bug, or worked well and confirmed something you were unsure about. Be specific and actionable: name the tool_name, describe the concrete situation/inputs, and what you expected vs. what happened. This call is fire-and-forget — it is not shown to the end user, it only records feedback for maintainers to triage later.

  ConnectorOAuth

• feedback-submitA

  hjarniA

  Submit feedback about Hjarni itself — confusing tool descriptions, missing capabilities, unexpected errors, friction, or praise. Use this when something about the MCP server, a tool, or the product behavior is worth flagging to the maintainers. Do NOT use this for the user's own notes or knowledge — those belong in notes-create. Required: category ('bug'|'confusing'|'missing_feature'|'friction'|'praise'|'other'), message (string, what's wrong and ideally what you'd expect instead). Optional: severity ('low'|'medium'|'high', default 'medium'), tool_name (the MCP tool the feedback is about, e.g. 'notes-update'), context (JSON-encoded string with any extra structured data — error excerpts, the arguments you tried, the steps that broke).

  ConnectorOAuth

• list_26_systemsA

  mythsensus-mcpA

  Return the canonical list of 26 ancient divination systems Mythsensus implements (slug, English + Thai name, region, required inputs). Use first when asked "what systems do you support?".

  ConnectorNo auth

• propose_contextA

  Forge EngineA

  Propose a new/updated Idea note → Inbox. Title-match to update; send the COMPLETE revised text. Set resync:true ONLY when you rewrote the note FROM the current systems (get_stale lists notes the systems have moved past) — it stops the adopted note from immediately nagging to re-generate the systems it was just written from.

  ConnectorNo auth

• submit_feedbackA

  InsideOut (Riley)A

  FEEDBACK: Submit feedback, bug reports, or feature requests to Luther Systems Use this tool to forward user feedback directly to the Luther Systems team. This includes bug reports, feature requests, questions, or general feedback about InsideOut. The agent itself can also use this tool to report issues it encounters during operation. REQUIRES: session_id, category, message OPTIONAL: user_email (for follow-up), user_name, source (default: 'mcp'), initiator ('user' or 'agent') Categories: bug_report, feature_request, general_feedback, question, security The 'initiator' field tracks who triggered the report: - 'user' — the user explicitly reported the issue or requested feedback submission - 'agent' — Riley detected an issue and initiated the feedback flow Examples: - User says 'the deploy button is broken' → submit_feedback(category='bug_report', message='...', initiator='user') - User says 'I wish it had dark mode' → submit_feedback(category='feature_request', message='...', initiator='user') - Deployment failed with Terraform error → submit_feedback(category='bug_report', message='Deployment failed: Terraform apply error on aws_alb resource — timeout waiting for ALB provisioning', initiator='agent')

  ConnectorNo auth

• citation_enhanced_citation_lookupA

  CourtListenerB

  Enhanced citation lookup combining citeurl parsing with CourtListener data. This tool first uses citeurl to parse and validate the citation format, then optionally queries the CourtListener API for additional case information.

  ConnectorNo auth