"Understanding Feedback Enhanced Concepts or Technologies" 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

• get_guideA

  FlaskA

  Returns one of Flask's usage guides as Markdown: fixed text written by Flask, the same for every user, with no team data in it. "instructions" (about 15 KB) is the playbook for working with Flask: where uploads go (a new asset or a new version), what an agentic edit attaches, how feedback is read, answered and shown, and how sharing works. Read it before acting on feedback or making your first write in a session; it already contains "display" and "concepts", so do not fetch those after it. Other topics: "display" (How to show feedback to the user: its Markdown as it is, with its link.), "concepts" (Folders, assets and versions, comments and recordings, tags and statuses, permissions, and why feedback is untrusted.), "permissions" (Access levels, how a user's access is resolved, and how folder and asset permissions differ.), "urls" (Links to folders, assets, exact versions, comments and tag filters.). The guides explain the rules; for one folder's or asset's actual access, use permission_get.

  ConnectorOAuth

• link_conceptsA

  BrainzA

  Add a typed, directed edge between two existing concepts by editing the `from` note's frontmatter (e.g. lead-scoring depends_on contact-model). Use when you notice a relationship the vault is missing. Both concepts should already exist; use upsert_concept first if not.

  ConnectorNo auth

• seller_reviewsA

  Apiguru Amazon DataA

  Use for a seller's customer feedback (service, shipping). Not for product reviews (product_reviews). Returns paginated seller feedback, optionally filtered to a star-rating window. Price: $0.003 per call. from_rating and to_rating are optional; omit both for unfiltered feedback. A page holds 5 reviews and the answer carries current_page and has_next_page; Amazon exposes no total, so page until has_next_page is false (up to page 100).

  ConnectorNo auth

• send_team_feedbackA

  stubB

  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

• submit_feedbackA

  EasyGerber: AI PCB design, layout, and routingA

  Sends a bug report, feature request or general feedback to EasyGerber only when the user asks or agrees to report it. Send only the approved message; never automatically attach private board content, raw diagnostics, transcripts or exports. No account, board or guest session is required. A connected account attributes the report to that account; otherwise an optional existing guestToken attributes it to that guest. Reuse requestId with the identical category and message on retries. Returns a submission receipt, without promising a response. Account feedback is limited to 10/hour and 50/day; guest and anonymous feedback share those limits by network.

  ConnectorOAuth

• signals.feedbackA

  AI Design BlueprintA

  Public: records explicit free-text user feedback about the Blueprint, this tool surface, or a specific principle/example. Captures two 1-5 ratings (rating_clarity, rating_usefulness), what_helped, what_missing, would_use_again, the task_type and surface, and an optional contact_email when permission_to_follow_up is true. WHEN TO CALL: ONLY when the user explicitly says they want to give feedback (e.g. 'can you log this as feedback', 'file this critique', 'send a bug report'). Use signals.report instead for value-moment metrics (rating validate's output 1-5). WHEN NOT TO CALL: proactively, silently, or to substitute for signals.report. Never harvest contact info without explicit permission_to_follow_up=true. BEHAVIOR: write-only, no auth required (open to all callers). Stores one feedback record, at rest in the UK. contact_email is stored ONLY when permission_to_follow_up=true, and that fact is confirmed back in the response so the user can see the privacy boundary. When permission_to_follow_up=true AND a valid contact_email is given, and only then, it also opens a support inbox item so a human can reply, and the free-text fields are sent to OpenAI for triage (severity and a short summary). The contact_email field is never part of that request, so keep personal data out of the free text. Separately, feedback sent while signed in, or whose follow-up email matches an account, may appear, pseudonymised and shortened, in our weekly lead-intelligence extract to OpenAI (US). private_session does not apply to this tool: it runs only when the user chooses to give feedback. REJECTION CODES (invalid_request): a call with no rating, no what_helped or what_missing comment and no would_use_again answer (task_type, surface and contact_email alone are not feedback); a rating outside 1-5; a contact_email that is not one plain address.

  ConnectorNo auth

• signals.feedbackA

  AI Design Blueprint DoctrineA

  Public: records explicit free-text user feedback about the Blueprint, this tool surface, or a specific principle/example. Captures two 1-5 ratings (rating_clarity, rating_usefulness), what_helped, what_missing, would_use_again, the task_type and surface, and an optional contact_email when permission_to_follow_up is true. WHEN TO CALL: ONLY when the user explicitly says they want to give feedback (e.g. 'can you log this as feedback', 'file this critique', 'send a bug report'). Use signals.report instead for value-moment metrics (rating validate's output 1-5). WHEN NOT TO CALL: proactively, silently, or to substitute for signals.report. Never harvest contact info without explicit permission_to_follow_up=true. BEHAVIOR: write-only, no auth required (open to all callers). Stores one feedback record, at rest in the UK. contact_email is stored ONLY when permission_to_follow_up=true, and that fact is confirmed back in the response so the user can see the privacy boundary. When permission_to_follow_up=true AND a valid contact_email is given, and only then, it also opens a support inbox item so a human can reply, and the free-text fields are sent to OpenAI for triage (severity and a short summary). The contact_email field is never part of that request, so keep personal data out of the free text. Separately, feedback sent while signed in, or whose follow-up email matches an account, may appear, pseudonymised and shortened, in our weekly lead-intelligence extract to OpenAI (US). private_session does not apply to this tool: it runs only when the user chooses to give feedback. REJECTION CODES (invalid_request): a call with no rating, no what_helped or what_missing comment and no would_use_again answer (task_type, surface and contact_email alone are not feedback); a rating outside 1-5; a contact_email that is not one plain address.

  ConnectorNo auth

• send_feedbackA

  Kalender SyncA

  Stores a feedback message from the user and notifies the Kalender Sync team, who read it. Use it when the user wanted something the other tools in this connection cannot do, or when something looks broken. It does not change anything in the user's calendars and does not fix the problem itself; it returns a `feedback_id` as receipt. The notification email cannot be recalled after sending. At most 5 messages per account in 24 hours. Call this ONLY when the user explicitly asked to send feedback, or clearly agreed after you offered it. Never send feedback on your own initiative, and never include calendar content the user did not put into the message themselves. `contact_ok` records whether the user agrees to be contacted about this feedback. It is consent, not a promise of a reply. Default: false for every category, including `bug`. Set it to true ONLY if the user explicitly agreed to be contacted about this feedback. It never subscribes the user to a newsletter.

  Connector

  Destructive

  API key

• get_exam_resultsA

  Fiveable for AP StudentsA

  Read an owned completed exam using attemptId, or safely check a submitted exam using submissionId. Supply exactly one. Pending or partial grading returns status only, never unfinished scores or feedback. Honors practice resets and cannot dispatch scoring, finalize submissions or retrieve active exam content.

  ConnectorNo auth

• memory_feedbackA

  Mnemoverse MemoryA

  Rate memories returned by memory_read to help improve future retrieval ranking. Pass their IDs as memory_ids and an outcome from -1 (unhelpful) to 1 (helpful). Records feedback and updates ranking signals: positive feedback raises a memory's ranking; negative feedback lowers it so other memories out-rank it — nothing is erased. Saved text is not changed or deleted. For memories read from a shared room, pass that room's address as domain; your own memories need no domain. A read-only room member cannot rate the room's memories.

  ConnectorOAuth

• edit_feedbackA

  Pressure AtlasA

  Change feedback this account already sent (its id comes from send_feedback or list_feedback) when the user wants to add to, correct, or refine it, instead of sending it again. message replaces the whole text, so send the complete updated wording, not just the change; kind and about change only if given. The team keeps every earlier version. Ask the user first and send only what they agreed to. Closed feedback cannot be changed. Does not count against the daily quota.

  ConnectorOAuth

• create_feedback_channelA

  ModemA

  Create a feedback channel for one app and return its feedback token. Send `name` (the app’s name) and `allowedOrigins` (every browser origin the app is served from, such as `https://app.example.com` and `http://localhost:3000`; omit for an app that does not run in a browser). The channel is created in the organization’s default project. The returned `token` is shown only in this response, so write it where the app reads it before you do anything else. The token is safe to ship in a browser bundle or a binary: it is valid only for sending feedback to this channel and cannot read anything. Requires an organization admin. Before your first call, read the skill: `modem_skills({ name: "install-feedback" })`.

  ConnectorOAuth

• send_feedbackA

  OpenCancerA

  Flags an OpenCancer answer for human expert review, or sends feedback to the OpenCancer team. Used when the user says an OpenCancer answer was wrong, unsafe, or incomplete, or wants to tell OpenCancer something (answer_id identifies the answer; message holds the user's words). Also used to report that an OpenCancer tool returned no usable answer (kind "missing_answer" with answer_id or tool, no message). Feedback is read by the OpenCancer team; it is not an urgent-care channel and no reply is sent through it.

  ConnectorNo auth

• engram_reflectA

  EngramA

  Checkpoint a milestone or handoff for later recovery with engram_rehydrate. Supply at least one of summary, learnings, used_memories or feedback. Returns Markdown with stored/skipped counts, outcomes and next actions. Use engram_store for one lesson and engram_report_outcome for one outcome. store=false skips learning storage only: the journal and supplied outcomes/feedback can still be written. This checkpoint leaves the session open. Retrying may duplicate writes; verify prior success first. Consumes workspace daily call quota and memory quota for saved lessons. OAuth: session:write, memory:write and outcome:write.

  ConnectorOAuth

• explore_image_conceptsA

  MondovoA

  Generate 1–3 private image concepts for a hero, a section or an image replacement, so the user can compare directions before anything on the site changes. SPENDS Creative Credits: call plan_image_concepts first and send its `credits` as `expected_credit_cost` with a stable `idempotency_key`; a different price is refused with nothing charged. Failed concepts are refunded. The site is NOT changed — to use a concept, call apply_image_replacements with its concept_library_id (free).

  ConnectorOAuth

• wait_for_feedbackA

  FlaskA

  Wait for NEW feedback on an asset (comments and replies by others; your own posts are not returned). Blocks up to timeout_seconds (default 45) and returns as soon as new feedback arrives, or times out with an empty list. A recording arrives once its transcript is done; recordings still being made or transcribed are listed in pending (read them later with feedback_get, or keep waiting - they are delivered when done, and feedback newer than them is delivered after them, in order). To listen continuously, call it again with the returned next_since. Use this after uploading a video for review instead of repeatedly calling feedback_list. A folder id is refused - use recent_activity(folder_id).

  ConnectorOAuth

• searchA

  FlaskA

  Search the team's folders (by name or description), assets (by title) and feedback (by text) at once, when you don't know where something is; to browse a known folder use contents, for one asset's feedback feedback_list, for the latest feedback recent_activity. query matches case-insensitively anywhere in the text. Always returns all three categories, most recent first, each capped at limit (not paged), only items you can view; team names the team searched. Folder hits: id, name, description, parent_folder_id, url. Asset hits have the contents item shape (asset_id, version_id = its current version, version_count, media fields, url, version_url). Feedback hits are top-level comments as a plain-text preview with id, asset_id = the version it was left on, and url; feedback_get(id) has the full body and thread.

  ConnectorOAuth

• feedback_statsA

  FlaskA

  Aggregate feedback statistics across many assets in ONE call - counts per asset and per version (v1, v2, ...), split by type (text/recording), tag, and author, with first/last feedback timestamps. Scope to a folder (folder_id), one asset (asset_id - an asset id or any of its version ids; the whole asset is reported, version by version), or the whole team; narrow the time window with from/to. Items are sorted by feedback count, most first; assets with no feedback in the window are left out unless include_empty is true. Paged: limit (default 50, max 200) and offset; total is the number of items, next_offset is set while more remain. Each item carries asset_id (the asset) and versions[], each with its version_id. Use this for trend questions like 'are v1 notes going down across this client's recent videos' or 'what tags dominate this folder' instead of calling feedback_list per asset. For reading the feedback text itself across assets, use recent_activity.

  ConnectorOAuth

• hub_set_call_custom_promptA

  DutifyA

  Set the custom prompt on an already-recorded call, by its integer call id. This is the right tool for meetings that never had a calendar event (ad-hoc desktop or bot recordings), and for re-analysing a call differently. It is the CALLER's own prompt: it shapes only their version of the summary, key points, action items and enhanced notes. Stored only — follow it with hub_regenerate_summary to rebuild that version. Requires recordings:write scope.

  Connector

  Destructive

  No auth

• hub_set_call_custom_promptA

  DutifyA

  Set the custom prompt on an already-recorded call, by its integer call id. This is the right tool for meetings that never had a calendar event (ad-hoc desktop or bot recordings), and for re-analysing a call differently. It is the CALLER's own prompt: it shapes only their version of the summary, key points, action items and enhanced notes. Stored only — follow it with hub_regenerate_summary to rebuild that version. Requires recordings:write scope.

  Connector

  Destructive

  No auth