Skip to main content
Glama
820,807 tools. Updated 2026-11-22 12:35

"A service for essay editing and feedback" matching MCP tools:

  • 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
  • Discover sheet names and used dimensions before reading or editing a WorkPaper. Returns metadata only; use read_range or read_cell for values.
    ConnectorNo auth
  • Report a problem with **the Partle marketplace API/MCP itself**. Authenticated. Prefer **OAuth**: connect once via the consent flow and the bearer token is attached automatically. **Fallback**: pass an `api_key` (prefix `pk_`, generate at /account). Required OAuth scope: `feedback:write`. Feedback is attributed to your account so reports are trustworthy and the channel can't be flooded anonymously. Scope — what this is for: - A Partle tool description is unclear or its parameters are surprising. - A Partle response is broken, malformed, or missing fields. - The Partle catalog is missing a category of products you'd expect. - Search relevance is off for a specific class of queries on Partle. Scope — what this is **NOT** for: - General complaints about tasks Partle isn't designed to do (Partle is a local-marketplace search/listing API — not a news API, an HTML hosting service, a portfolio-rebalancing app, a stock brokerage, or a generic dashboard SaaS). - Venting that an invented API key was rejected (Partle keys must be `pk_<hex>`; generate one at /account — don't fabricate them). - Asking the maintainers to do work the user requested but you can't do. If you can't fulfil a user request, tell the user — don't submit feedback about it here. Don't loop — each call adds a row and pages the maintainer. Resubmitting the same text within 24h is de-duplicated (returns the existing id). Args: feedback: Freeform text up to 5000 characters. Be specific — name the tool, the input that was confusing, and what you expected. api_key: Optional API key (`pk_*`, generate at /account). Used when there is no OAuth token, and also when the OAuth token lacks the required scope — an explicitly passed key overrides an ambient token that is scoped too narrowly. An invalid or revoked token still fails regardless. Omit when using OAuth. Returns: ``{"id": int, "message": "Thanks for the feedback!"}`` on success, or ``{"error": ...}`` on auth, rate-limit, or validation failure.
    ConnectorNo auth
  • Report a problem with **the Partle marketplace API/MCP itself**. Authenticated. Prefer **OAuth**: connect once via the consent flow and the bearer token is attached automatically. **Fallback**: pass an `api_key` (prefix `pk_`, generate at /account). Required OAuth scope: `feedback:write`. Feedback is attributed to your account so reports are trustworthy and the channel can't be flooded anonymously. Scope — what this is for: - A Partle tool description is unclear or its parameters are surprising. - A Partle response is broken, malformed, or missing fields. - The Partle catalog is missing a category of products you'd expect. - Search relevance is off for a specific class of queries on Partle. Scope — what this is **NOT** for: - General complaints about tasks Partle isn't designed to do (Partle is a local-marketplace search/listing API — not a news API, an HTML hosting service, a portfolio-rebalancing app, a stock brokerage, or a generic dashboard SaaS). - Venting that an invented API key was rejected (Partle keys must be `pk_<hex>`; generate one at /account — don't fabricate them). - Asking the maintainers to do work the user requested but you can't do. If you can't fulfil a user request, tell the user — don't submit feedback about it here. Don't loop — each call adds a row and pages the maintainer. Resubmitting the same text within 24h is de-duplicated (returns the existing id). Args: feedback: Freeform text up to 5000 characters. Be specific — name the tool, the input that was confusing, and what you expected. api_key: Optional API key (`pk_*`, generate at /account). Used when there is no OAuth token, and also when the OAuth token lacks the required scope — an explicitly passed key overrides an ambient token that is scoped too narrowly. An invalid or revoked token still fails regardless. Omit when using OAuth. Returns: ``{"id": int, "message": "Thanks for the feedback!"}`` on success, or ``{"error": ...}`` on auth, rate-limit, or validation failure.
    ConnectorNo auth
  • Create an amendment to a SIGNED parent contract. Scope delta required; fee delta and target date optional. Returns the draft amendment for editing before send — call contract_send with the returned amendment id to fire it. Cannot amend an amendment (amend the parent instead).
    ConnectorNo auth
  • Free. Sends a message to the human operators of this service: a bug report, a problem with these tools or the documentation, or a suggestion. It is read by people, not processed by software, and nothing is returned beyond an acknowledgement. Do NOT use it for status updates, progress notes, task narration, error logs, or as a fallback when another tool is unavailable or a payment cannot be made -- it cannot complete, retry or work around any task. Name is optional (omit for anonymous feedback); message is limited to 1000 characters.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • Read and resolve the bugs, ideas and survey answers your users send through Melonhelp Feedback.

  • Capture feature requests and bug reports from chat into a searchable, AI-categorized backlog.

  • Use this when you need to review what a Study found: aggregate evidence, findings, citation references, freshness and next action. Standard connections also receive paginated individual rating feedback by default. Managed connections return aggregate findings by default; includeFeedback=true requires original-source permission and adds the feedback feed with participant identity. feedbackLimit and feedbackOffset page that feed. Use studies.get_responses for individual research answers; that is a separate original-source read.
    ConnectorOAuth
  • Get one Durability Curve essay: by default its full public text as markdown, with its title, dates, canonical field, access, length, sections, tools and a link to its claim ledger when it has one. A long essay can be read in parts: part "outline" lists the sections with their opening lines, part "section" returns one, and part "meta" returns everything but the text. For a part-paid essay only the free part is public, and the text says where it stops. The canonical field is the address to cite. These tools retrieve The Durability Curve's public material. They do not certify that any claim is true.
    ConnectorNo auth
  • 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
  • Record the user's feedback on a scan. The scan reads it while it runs. Trent reasons from code, sites, and documents. Feedback supplies intent, deployment facts, and accepted risks that those sources cannot show: "that host is internal", "we accept that risk", or "this finding misreads our auth flow". Use this for feedback that needs reasoning. Use edit_analysis for a mechanical correction to one field of one finding. Record the feedback the user expresses in their current message, in their own words. A correction in passing counts as a request to record it. Do not reconstruct feedback from earlier turns, infer or embellish it, or resubmit it on your own initiative; that can invent the user's intent. Do not record feedback twice, even if an earlier item is missing from a listing; recording it again creates a duplicate. Each item is acted on by one stage, so record one item per claim, each with its own stage_id. Do not add items for effects the user did not state: "we added Redis as a cache" is one item at understand. A consequence the user states ("so F-12 should be Low") is its own claim. One fact that explains several findings is one item at understand that names them; accepting a risk is one item at secure. Repeat a shared reason in each item so each stands alone. Tell the user how you split their message, listing only the items that recorded. Name the project with project_id or project_name; with neither, the call is refused. Check attached_to_scan. When false, say the feedback is stored without a scan to read it. A target naming a requirement that is not in the project's current list is refused with reason unknown_target.
    ConnectorOAuth
  • Plaintext logins captured by the interactive sensors (sensors that answer as a real service and hold the session): username, password, the service they were tried on, the outcome and the source address, newest first, plus the pairs tried most and a per-service breakdown. Use for "what passwords are attackers trying on SSH", "which credentials did this IP try", "what logins hit MySQL this week". For whether an address is hostile overall, use ioc_lookup_tool; for the rest of what it did in its sessions, use interactive_sessions_tool. service: a service name such as ssh-password, telnet-login, mysql-login, rdp-credssp or smb-ntlmssp, or empty for all. source: an address or CIDR, or empty for all. window: 24h, 7d (default) or 30d, capped at the plan's query window. limit: 1 to 200, default 50. These records feed no verdict, and ioc_lookup_tool does not include them.
    ConnectorNo auth
  • Plagiarism checker. Use when the user wants to know whether a text, such as an essay, research paper, thesis, article or blog post, copies or closely matches web sources. Starts a check in the background and returns a scan_id with status pending; the result is not in this reply. Then call get_scan_result with that scan_id. Uses one word from the user's balance for each word checked, so calling it again on the same text charges again. The text needs at least 30 words. If it is too short, too long for the user's plan, or the balance is too low, nothing is charged and the reply explains why. For likely AI writing, use detect_ai instead.
    ConnectorOAuth
  • Submit only the feedback the user explicitly asks to send to AiLinkAny. Requires user_confirmed=true, BUG/FEATURE/OTHER, a short message and a fresh opaque 32 lowercase hex feedback_id. Reuse that ID only for the same submission after transport failure. Never automatically upload files, logs, credentials or competitor feedback; suspected secrets are rejected. At most two new submissions per 10 minutes. Account OAuth identity is authoritative and no device/subscription is required.
    ConnectorOAuth
  • Post the saved feedback preview under the connected user's public cobuild account. The mod's maintainer is notified as for a comment on the website. Requires explicit approval of the exact action and public text. Pass the draftId from prepare_feedback, its unchanged digest and consentVersion (agent-feedback-v1), and approved:true only after that approval. OAuth consent is not approval. Retrying the same draftId never posts twice. An expired draft needs a new preview and approval.
    Connector
    Destructive
    No auth
  • 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
  • Verify a single image's authenticity when the user asks whether it is genuine, AI-generated, manipulated, or carries Content Credentials, and only the image is available (no RAW camera file). Not for feedback on a photo (composition, editing, colour) or for anything that is not a still image. Checks its embedded Content Credentials (C2PA) for capture provenance and AI-generation flags, and runs advisory forensic screens (error-level analysis, double-JPEG artifacts, EXIF timestamp consistency, editing-software traces, screen recapture). Free: it does not consume your verification quota. Provide the image as an attachment (image_file), inline as image_base64, or — for large files without attachments — call create_verification_upload and pass the returned image_object_key. Returns a verification id at once; the analysis runs in the background and takes from about a minute to 10 minutes or more, so call get_verification with the id repeatedly until status is completed; the completed result includes a structured evidence_report (verdict, per-check findings, coverage). For the strongest forensic check, use verify_photo with a RAW + JPEG pair instead.
    ConnectorOAuth
  • Search the SMS VERIFICATION service list — websites/apps a receive-only verification number can get a code for (Telegram, WhatsApp, Instagram / Threads, ...). Not offered for financial services, gambling, or government / identity-proofing services; delivered codes are capped per service per wallet (5 per 24h, 20 per 30d). This is the SMS product line (no eSIM, nothing to install): the user gets a temporary phone number and reads the incoming code. Returns service names with their serviceId in [brackets], most relevant first, 100 per page. If the target service is not listed, search "Other" — the catch-all works for any site. Next step: get_sms_service_countries.
    ConnectorNo auth
  • 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
  • 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
  • USE WHEN an agent needs another agent for a task and wants the pick explained by registration, answering service, feedback and liveness. Candidates are the listed Sato Agent Passports; the top 3 by the static ranking get one live MCP handshake before the pick is made. NOT FOR browsing registered agents with filters (use onchain_agent_search_agents instead) or one agent's manifest (use onchain_agent_get_agent_passport). RULE ENFORCED: a route is a RECOMMENDATION, chosen by the listed fields at checked_at. `chosen_by` names every signal, its value and the exact field it was read from. An ERC-8004 registration proves a claim was made on-chain, not that the agent works; wallet_verified proves the key, not the product; a probe proves the declared service answered once. A null feedback count is unknown and ranks below every number, including zero. No job-outcome data exists yet. COVERAGE: agents registered on-chain but holding no Sato passport are absent from the pool — there is no keyless ERC-8004 enumeration callable from a request. Absent means unseen, not unqualified. When nothing qualifies the answer is `unknown` with a reason, never a low-confidence pick. RETURNS (json): { route: { agent, chosen_by: [{ signal, value, source_field }], checked_at, alternatives: [{ id, name, source, behind_on }], caveat } | { unknown, reason }, preflight, candidates_considered, probed, coverage, rules, caveat, checked_at }. Example: { capability: "trading", chain: "Base", requires_mcp: true }
    ConnectorNo auth
  • 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