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

"A guide to writing reports" matching MCP tools:

  • What to know before going to a venue, from UPFRONT's venue guide: the bag policy and what fans can bring, gates and entry, parking, getting there by transit or rideshare, and food and drink, including what the guide says about gluten-free, vegetarian or vegan, halal and kosher food. Matches questions like "what's the bag policy at MetLife?", "when do doors open at MSG?" or "where do I park for Lambeau?". venue: the venue's name ("MetLife Stadium", "MSG", "Lumen Field, Seattle"). topics: optional; only these parts, at more length: any of "bags", "entry", "parking", "transit", "food". Without it, every part. Covers the 36 stadiums, arenas and amphitheaters UPFRONT has a guide for; for any other venue the answer says so and lists the ones with guides. Each part is the guide's own words ("text", plus the guide's "faq" questions and answers). factsLastChecked is the date UPFRONT last checked the guide's facts; rules can change for a single event, and the venue's own event page has the final word. guideUrl is the guide on UPFRONT. dietary lists what the guide says per diet; dietaryNotMentioned lists diets the guide doesn't cover, which doesn't mean the venue has nothing for them.
    ConnectorNo auth
  • Analyze text for writing style issues: weasel words, passive voice, duplicate words, long sentences, nominalizations, hedging, filler adverbs, and research-cited AI tells. Read-only and stateless — text is analyzed in memory on the hosted server and never stored. Returns a plain-text report with each issue's line and column, the matched text, surrounding context, and the reason for AI tells; texts over 100,000 characters return an error message. This hosted server has no filesystem access — the wsc-mcp npm package adds a check_file tool for local files. It only reports issues — to auto-remove duplicate words, follow up with fix_duplicates.
    ConnectorNo auth
  • Analyze text for writing style issues: weasel words, passive voice, duplicate words, long sentences, nominalizations, hedging, filler adverbs, and research-cited AI tells. Read-only and stateless — text is analyzed in memory on the hosted server and never stored. Returns a plain-text report with each issue's line and column, the matched text, surrounding context, and the reason for AI tells; texts over 100,000 characters return an error message. This hosted server has no filesystem access — the wsc-mcp npm package adds a check_file tool for local files. It only reports issues — to auto-remove duplicate words, follow up with fix_duplicates.
    ConnectorNo auth
  • Create new guides Create one or more new guides based on provided queries. Each guide targets exactly ONE engine and ONE analysis mode, chosen with the optional `source` field (default `google`). How to request each guide type: 1. Google SERP guide (1 credit per guide): omit `source`, or pass `source: "google"`. Example payload: {"queries": ["best crm"], "lang": "en-us"} 1bis. Google AI Overview guide (1 credit per guide). Two modes, like AI engines: `source: "google_ai_overview"` builds the guide from the TEXT of Google's AI answers (AI Overview, completed with AI Mode answers) ; `source: "google_ai_overview_citations"` builds it from the content of the web SOURCES those answers cite (recommended for GEO). Same language/country parameters as a Google SERP guide, 1 credit per guide in both modes. Example payload: {"queries": ["best crm"], "lang": "en-us", "source": "google_ai_overview_citations"} 2. LLM ANSWER guide (4 credits per guide): pass the engine name alone, e.g. `source: "chatgpt"`. The guide is built from the answer text the AI generates for the query. Example payload: {"queries": ["best crm"], "lang": "en-us", "source": "chatgpt"} 3. LLM CITATIONS guide (4 credits per guide) [RECOMMENDED AI mode]: pass the engine name with the `_citations` suffix, e.g. `source: "chatgpt_citations"`. The guide is built from the content of the web pages the AI cites in its answer. Example payload: {"queries": ["best crm"], "lang": "en-us", "source": "chatgpt_citations"} Which AI mode to pick? For GEO (getting a page visible in AI answers), prefer `<engine>_citations`: AI engines send traffic by CITING pages as sources, so the winning move is to look like the pages they cite. The answer-text mode (`<engine>` alone) is mostly useful to analyze how the AI phrases its own answer. When in doubt, pick `<engine>_citations`. The same two modes exist for every AI engine (chatgpt, perplexity, claude, gemini, grok, mistral, deepseek). To optimize the same page for several engines or modes (e.g. Google AND ChatGPT answers AND ChatGPT sources), create one guide per source value on the same query. IMPORTANT, HOW TO READ THE RESPONSE OF THIS ENDPOINT, WHICH SPENDS CREDITS. Queries listed in `guidesFailed` are PROVEN not to have produced a guide and their credit was given back (unless the account has unlimited credits, where nothing was reserved): re-sending them is free and correct. Queries listed in `guidesUnknown` have an UNDECIDABLE outcome and their credit is deliberately KEPT, because the guide was most likely written: DO NOT re-send them, you would pay for the same guide twice. Look them up in `GET /api/v1/guides` after a few minutes instead, and contact support if nothing shows up. Finally, a `200` is NOT a promise that every query produced a guide: compare `guides.length` with the number of queries you sent, never read `success` alone, and never re-send a query just because it is missing from `guides`.
    ConnectorNo auth
  • Reports a problem with homespun itself to the relay operator, and lists what this agent has already reported. A report is the operator's only visibility into a failure that happened inside an agent's session, so an unreported one is a failure nobody can fix. The channel covers homespun's own behaviour: a 5xx, or an error code the guide does not describe; a disagreement between documented and observed behaviour; something the tool surface cannot express, such as a missing capability or a schema that contradicts itself; an app misbehaving in a way that traces back to the platform (the bridge, the runtime, serving, the data API) rather than to authored HTML; or a guide that was wrong, ambiguous or silent. Outside its scope: the human's own task; bugs in an app the agent authored; presentation preferences, which belong in `taste`; the human's own configuration, such as a missing API key or the wrong account; and a 4xx caused by the agent's own arguments, except where the error message itself was misleading, which is a documentation problem best filed as a `note`. Duplicates cost the operator triage rather than adding signal. Action `list` returns this agent's own submissions, newest first, so a failure already recorded needs no second row: one report covers one distinct failure, however many times it was retried. The operator sees the row and not the session, so a bare "deploy failed" is not actionable. An actionable `message` carries the surface (mcp, cli, relay or app-runtime); where it happened (the tool or route); the skill version, from the `<!-- homespun skill vX.Y.Z -->` comment at the top of the guide; what was expected, in one line; what was observed, in one line carrying the exact error code and message; and the minimal steps or arguments that reproduce it. `type` is bug for something broken, feature for something missing, note for a rough edge or a confusing doc. `app_id` scopes a report to one app. There is no reply channel, so a report is not a route to an answer. Actions: create files one report; list returns this agent's own submissions, newest first, paginated by `before`.
    ConnectorNo auth
  • Preview, without writing, how one completed owned Accounting run's WRITEOff work plan would map to stable Meta Council tickets. Reports creates, updates, unchanged tickets, human-edited generated fields that will be preserved, and identity conflicts. Requires both accounting:read and tickets:read; tickets:write also satisfies the ticket-read grant. Preview before committing because tickets are not field-encrypted; work-plan text may reproduce source-derived snippets or parser details, and after commit tickets:read can read it without accounting:read. Check the item count before committing. Statement-derived runs currently plan one ticket per unclassified transaction line, so a several-hundred-row statement plans several hundred tickets. When the count is large, report it and confirm with the owner rather than committing a board-flooding sync.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    面向 Codex、WorkBuddy 等 AI 工具的知你AI助手合并版 Skills,涵盖当前会话分诊、客户查询与画像、历史会话检索、客户分群和 API Key 用量查询,并连接个微、企微、视频号、微信小程序、公众号、服务号、微信客服、微信小店、抖音号、小红书、微博、网站及H5客服等渠道。
    MIT No Attribution
  • A
    license
    Not graded
    quality
    C
    maintenance
    这是面向智能运维场景的 MCP 工具服务,让 Agent 能够按需检索日志内容并获取主机与应用的监控指标数据。它把实时的日志与指标证据接入 Plan-Execute-Replan 诊断流程,从而支撑自动故障排查与根因分析。
    3
    MIT

Matching MCP Connectors

  • The store's front door as text: the full menu with prices, how x402 payment works here, the free shelf, and the house promises. Free. Completes when the guide text returns. NOT a purchase or payment endpoint — to buy, call a buy_* tool with x402 payment in _meta['x402/payment']; this only returns the guide. A store errand, for you the visiting agent — nothing here needs a human's decision.
    ConnectorNo auth
  • Replace the notes on a finished Load Test's Test Report — the only thing on a Load Test this surface edits. Ask the user before writing: notes belong to the user, and advising on a test never requires writing them. The text sent becomes the report's entire notes, so first read the current notes with get_load_test_report and preserve the user's content in what you send.
    Connector
    Destructive
    OAuth
  • How this Aevia connection works, plus playbooks for results, reports, systems. Returns a skill's playbook as the result; takes no action itself. A playbook is step-by-step guidance for a multi-step job, too long for a description. `connector_guide` covers how this connection works: workspaces, refs, finding data, the library, building, calculating and failures. `assessment_interpretation` covers reading and comparing results: what an indicator result is and is not, a figure's anchors, functional-unit equivalence and comparison discipline. `report_writing` covers writing results up as a document, from a screening note to an ISO 14044 study. `product_system_authoring` covers building a new product system with `lca_compose_assembly` / `lca_compose_linked`: build order, which of the two fits, failure modes, and tagging life-cycle phases. A loaded playbook stays in context; one load per session suffices. Skills are gated on what the token can call; an unavailable request returns the available list.
    ConnectorAPI key
  • Applies a tag to one or more contacts (max 100). Get the `tagId` from list_tags (or from create_tag for a new one). Idempotent: contacts already tagged are ignored. Each application emits the contact.tag_added event: use list_automations to see which automations listen to that event before writing.
    ConnectorAPI key
  • Replace an existing interview guide from markdown. To create the first guide, call guides_create. Text before the first ## is the intro. ## Title (12) or ## Title (7–11) is a block; minutes are the last number in parentheses. Lines starting with - or 1. are questions; a leading * marks a key question; the next indented line is the question note. A paragraph under the block heading before the first question is the block note. ## Конспект is the post-interview notes template, not a block. Optional line `Общее время: 30` or `Total: 30` sets total minutes; otherwise they are the sum of block minutes. Anything that does not match is returned in remainder and kept, not dropped. The previous guide is replaced entirely.
    Connector
    Destructive
    OAuth
  • A short research report on what a link or a topic means for one coin, grounded in the coin's dashboard, with its own public page to share. To ask: pass symbol and about (a public http(s) link such as a post on X, a press release or an article, or a topic of 3 to 300 characters); the answer comes at once with status=writing and the report's id. To read: pass report_id (no key needed); status is writing, ready or unavailable. At most 6 reports an hour and one a minute. The report is written by EventTrader's AI and can be wrong. Asking needs a registered agent (API key). From EventTrader's crypto dashboards (cymetica.com/crypto). Every number carries its source and time; a number that failed a plausibility check is withheld, never guessed. Places no orders, moves no funds. Not financial advice.
    ConnectorNo auth
  • Start tracking search terms for one of your apps, in one storefront. Send terms, or `keyword_ids` for suggestions returned by discover_keywords — a suggestion MUST be added by id, because re-resolving its term can land on a different keyword row. Counts against the plan's per-app keyword limit; `dry_run` reports what would happen without writing anything. Terms already in the corpus come back under `already_tracked` rather than as an error — that is the state the caller asked for.
    ConnectorNo auth
  • Tell the team you are writing a reply to an email thread, so getThreadTeam and the app show the others that you are replying and nobody answers twice. The mark lasts 30 seconds, so call it again while you are still writing, and with replying false once you have sent the reply or given up.
    Connector
    Destructive
    OAuth
  • Optionally record a technical problem, suggestion or neutral successful outcome using fixed choices. Use after communicating the outcome to the buyer; never required to buy a card. Reports are stored for 30 days and deduplicated daily. Returns recorded or duplicate; TRY_LATER means the daily limit of 100 new reports per server-assigned scope or 500 overall was reached. Do not include personal content, credentials, links, conversations or hidden reasoning. Reports are unverified feedback, not proof of payment or mailing.
    ConnectorNo auth
  • Which USDA AMS daily cash grain bid reports exist, which state and commodities each covers, and how fresh each is. FREE. Call before cash.bids to learn which states are covered and which reports have stopped publishing: liveness is current, stale (served and flagged), unlisted (AMS no longer lists it) or unknown. Three reports are published as covered-but-unparsed rather than omitted, because a visible gap beats a silent absence.
    ConnectorNo auth
  • Admin only. Saves (creates or updates) the DRAFT of an Equitest Insights M&A report for one period. The numbers, charts and tables on the page are recomputed on the server from the database — only the text is taken from here. Nothing goes live: the admin opens the returned preview_url on equitest.net and clicks Publish. A published report cannot be changed here — unpublish it on the site first. Follow the writing guide returned by ma_period_digest.
    ConnectorOAuth
  • Change the project's writing voice (Project Settings > Voice): the voice guide, words to avoid, and formatting rules. Every post, article and slide the app writes follows these, and so must you. Each field you pass REPLACES that field, so read flypost_get_writing_voice first and send the full new text (e.g. add a word to the existing avoid list, do not send just the new word). Pass null to clear a field. Change them when the user asks you to remember a style rule.
    Connector
    Destructive
    OAuth
  • Finds the official reference page for exact WordPress names: functions, hooks, classes, methods, WP-CLI commands, REST routes, core blocks and @wordpress packages. Use before writing or reviewing code that calls one, to confirm it exists in WordPress core, since which version, and whether it is deprecated. Pass up to 8 names in one call. Returns links with a one-line summary, never the page content; a name that is not in WordPress core is reported as not found. For a guide or a plugin's documentation, use wp_docs.
    ConnectorNo auth
  • Update global reminder settings. Writable fields are only enabled and daysBefore (1, 3, 7, or 14). timeZone, locale, Bark URL, and test push are not writable. Confirm with the user before calling (riskLevel: medium). Requires the 'write' API key scope. Use when: The user asks to turn global reminders on or off, or change the advance reminder window. Do not use when: The user wants to paste a Bark URL, change timezone/locale, or send a test push. Notification settings do not exist yet (API returns 404); tell the user to configure Bark once in the web app first. Do not claim you can configure Bark URL/device key, send a test push, change timeZone/locale, or manage the category catalog. Those stay in the web app. If the user asks to paste a Bark URL or run a test push, refuse and point them to Settings → Notifications in the web app, and to the reminders guide at /docs/en/user-guide/reminders (Chinese: /docs/zh-CN/user-guide/reminders). After Bark is configured on the web, you may toggle enabled/daysBefore and per-subscription notificationEnabled.
    Connector
    Destructive
    No auth
  • Scaffold a flags-only Bridge integration into an existing project — the MCP equivalent of `bridge flag init`. Returns everything that command produces, for YOU to write to disk: the contents of bridge-flags.config.json (app id, app name, base URL, suggested provider config, read live from this Bridge app), the install command, and the framework-specific setup guide fetched from the plugin repo that owns it. Writes nothing — neither to disk nor to the Bridge app. Call this when adding feature flags to a project for the first time; for auth or billing use get_integration_guide with topic=master or topic=billing-master instead. framework is REQUIRED: this server cannot see the caller's disk, so detect it yourself from package.json (next → nextjs, @sveltejs/kit or svelte → svelte, @nestjs/core → nestjs, @angular/core → angular, react → react, express → express; check in that order) and pass it. The returned guide is the same document get_integration_guide returns for topic=feature-flags, so there is no need to call both. Do not invent import specifiers — they differ per plugin and only the guide has the current ones.
    ConnectorOAuth