Skip to main content
Glama
127,531 tools. Last updated 2026-05-05 21:04

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

  • Collects user feedback on the provided response. **When to use this tool:** - After providing an analysis, a SQL query, or an important response - When you want to know if the response was helpful - Naturally suggest: "Was this response helpful? 👍 👎" **Ratings:** - 'positive': The response was helpful and accurate - 'negative': The response was not satisfactory - 'neutral': Neither satisfied nor dissatisfied **Categories (optional):** - 'accuracy': Was the response accurate? - 'relevance': Did the response address the question? - 'completeness': Was the response complete? - 'speed': Was the response time acceptable? - 'other': Other feedback **Feedback usage:** Feedback is used to improve future responses (RAG, analytics).
    Connector
  • Rate an AI agent after completing a task (worker -> agent feedback). Submits on-chain reputation feedback via the ERC-8004 Reputation Registry. Args: task_id: UUID of the completed task score: Rating from 0 (worst) to 100 (best) comment: Optional comment about the agent Returns: Rating result with transaction hash, or error message.
    Connector
  • Given a passage of text (essay, note, message, snippet, transcript), returns ~5 humans whose intellectual fingerprint matches it — recurring themes, mental models, archetypal stance, blind spots. Use when the principal asks for sparring partners, intellectual peers, "who else is wrestling with this," "who thinks like X," or "find me writers similar to this passage." Each result returns a name, three-word archetype, one-line summary, dominant themes, and a profile URL the principal can visit. The match runs over Voyage 3.5-lite text embeddings reranked by a proprietary 12-dimensional cognitive-style vector — so results align by *how* a mind reasons, not just topical overlap.
    Connector
  • Get an exact sat cost quote for a service BEFORE creating a payment. Useful for budget-aware agents to price-check before committing. No payment required, no side effects. Pass service=text-to-speech&chars=1500, service=translate&chars=800, service=transcribe-audio&minutes=5, etc. Returns { amount_sats, breakdown, currency }. Omit params to see the full catalog of supported services.
    Connector
  • Search for businesses and service providers on the Dashform marketplace. Filter by category, location, or keyword. Each result includes a funnel_id you can use with get_business_info, get_services, check_fit, and book_appointment.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • AI-to-AI petrol station. 56 pay-per-call endpoints covering market signals, crypto/DeFi, geopolitics, earnings, insider trades, SEC filings, sanctions screening, ArXiv research, whale tracking, and more. Micropayments in USDC on Base Mainnet via x402 protocol.

  • French public services: tax, property, admin, education, healthcare, security, risks, legal texts

  • Get upcoming vessel arrivals and departures at a specific port. Use this to check what vessels are expected at a port — useful for booking planning and tracking. Returns vessel names, carriers, ETAs/ETDs, and service routes. For transit time estimates between two ports, use shippingrates_transit. For detailed service-level routing, use shippingrates_transit_schedules. PAID: $0.02/call via x402 (USDC on Base or Solana). Without payment, returns 402 with payment instructions. Returns: Array of { vessel_name, carrier, voyage, eta, etd, service, from_port, to_port }.
    Connector
  • Quote price for a service at a business. Deterministic lookup of pricing_json_v2.ranges[]; LLM fallback on miss, labelled 'estimate' with disclaimer.
    Connector
  • List past orders with optional filters for status, service, country, and a lookback window in days. Returns up to 50 orders (server cap) ordered most-recent-first.
    Connector
  • Deploys a Cloud Run service directly from local source files. This method is suitable for scripting languages like Python and Node.js, of which the source code can be embedded in the request. This is ideal for quick tests and development feedback loops. You must include all necessary dependencies within the source files because it skips the build step for faster deployment. **Key Requirements:** 1. source_code: Should set to sourceCode.inlinedSource.sources with array of source files, each having `filename` and `content`. 2. Size limit: you are subject to total request size limit of 50MiB.
    Connector
  • 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')
    Connector
  • Read incoming feedback for THIS session's project. Returns bug reports, feature requests, usability notes, and success stories that other Claude sessions (or the project owner) have submitted via report_issue, filtered to this session's project. Lets Claude review what's coming in without needing the admin dashboard. Scope is strictly "this session's project" — determined by the project_key used at create_session time and stored in the session. You cannot read another project's feedback with this tool. Args: key: Session key secret: Session secret from create_session category: Optional filter — "bug", "feature_request", "usability", "documentation", or "success_story". Empty = all categories. limit: Max rows to return (default 20, capped at 100). Returns: {project_key, count, feedback: [{id, category, description, git_user, created_at, shipped_in_build, published}, ...]} or {error: "..."} on bad auth / missing project.
    Connector
  • Send freeform feedback about your experience using Partle. Use when you encounter a confusing tool description, a broken response, missing data, or anything you'd want the maintainers to know. Especially valuable for AI agents — your feedback is a tuning signal we use to improve the API. Don't loop (each call adds a record). Not idempotent. No PII required. Args: feedback: Freeform text up to 5000 characters. Be specific — name the tool, the input that was confusing, and what you expected. Returns: ``{"id": int, "message": "Thanks for the feedback!"}`` on success, or ``{"error": ...}`` if the input is empty or too long.
    Connector
  • FREE — Submit feedback about any Agent Safe tool you used. Helps us improve detection accuracy and tool quality. No charge, no authentication required.
    Connector
  • Add a review/rating for a completed task. Rate the operator's work quality. This is separate from approve/reject — it records feedback. Requires authentication.
    Connector
  • Records explicit user feedback — open to all callers, no auth required. Call ONLY when the user explicitly says they want to give feedback; never proactively. contact_email stored only when permission_to_follow_up is true — confirmed in response.
    Connector
  • Query available time slots within a date range. Agenda-aware: without clientId, filters by the org default public agenda — each org decides which services to expose. With clientId, resolves the client titular provider and returns their full service catalog. Five modes: (1) orgSlug only — slots from the public agenda grouped by service, provider auto-assigned at booking; (2) orgSlug + clientId — resolves titular provider if set, falls back to agenda; (3) orgSlug + agendaId — slots for a specific agenda; (4) serviceId — slots for all providers assigned to that service; (5) providerId — slots for a specific provider. Modes 1–3 hide provider details. Use before booking_create.
    Connector
  • Book an appointment with a local service business. Creates a booking record and adds the appointment to the business calendar. Returns a reference number and a status field indicating the actual resulting state — 'pending' (the business reviews each booking), 'confirmed' (auto-approved by the business), or 'completed' (the business auto-finalizes). Read the status and statusDescription verbatim and relay them accurately: do NOT tell the customer 'confirmed' when the status is 'pending'. If the selected service has requiresCustomerAddress=true, ask the customer for their full service address before calling this tool and pass it as customerAddress. ONLY call this if the business has 'booking' in its enabledFeatures array.
    Connector
  • Assess email attachments for malware risk based on filename, MIME type, and size BEFORE opening/downloading. $0.01/call via skyfire-api-key header (Skyfire Buyer API Key). By using this service you accept the Terms of Service. Advisory service only.
    Connector