Skip to main content
Glama
683,909 tools. Updated 2026-10-21 08:42

"A guide for writing research reports" matching MCP tools:

  • 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
  • Open-ended discovery across SMI deep reports, research bundles, and exports when you do not already have a record id — finds candidates by subject name, url, or keyword and returns typed references to pass to fetch. If you already have a record id from the conversation rather than from a search result, call the specific tool instead: smi_get_deep_report or smi_get_export to read one record, smi_check_order_complete for order readiness, smi_list_deep_reports or smi_list_exports for filtered listings, smi_get_report_findings for findings within a report. Deep reports and research bundles are filtered server-side by subject first/last name, broadening to an unfiltered fetch ranked client-side (across id, name, url, summary) when the filtered fetch finds nothing; exports match on url.
    ConnectorOAuth
  • 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

Matching MCP Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    An MCP service for AI-assisted reasoning and editing on long-form fiction projects. It builds a structured index from scene files for targeted context retrieval.
    130 npm
    1
    AGPL 3.0
  • F
    license
    Not graded
    quality
    D
    maintenance
    Pulls golf data from Arccos, GHIN, and 18Birdies, and generates interactive HTML and PDF round reports with shot maps and stats via local MCP tools.
    -

Matching MCP Connectors

  • 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
  • Discover deterministic top-level JSON field validation for API payloads, automation and AI-agent handoffs. The value must be an object; schema.required finds absent fields, schema.properties.<field>.type finds primitive type mismatches, and additionalProperties=false reports unknown fields. Prefer this for new simple contracts and use json_schema_check for nested or recursive constraints. This free MCP discovery call does not execute the advertised capability and does not charge; it returns the exact x402 endpoint, price and payment guide for execution.
    ConnectorNo auth
  • Discover deterministic top-level JSON field validation for API payloads, automation and AI-agent handoffs. The value must be an object; schema.required finds absent fields, schema.properties.<field>.type finds primitive type mismatches, and additionalProperties=false reports unknown fields. Prefer this for new simple contracts and use json_schema_check for nested or recursive constraints. This free MCP discovery call does not execute the advertised capability and does not charge; it returns the exact x402 endpoint, price and payment guide for execution.
    ConnectorNo auth
  • Get Lenny Zeltser's expert writing guidelines for security reports and assessments. Provides guidance on tone, structure, clarity, executive summaries, and avoiding common writing mistakes. Includes rating-sheet items (the four lens sheets: structure, look, words, tone) as concrete reference points for grounded feedback. Works for any security document. This server never requests your documents and instructs your AI to keep them local—guidelines flow to your AI for local analysis. Note: For incident response reports specifically, use the ir_* tools which provide deeper section-by-section review criteria.
    ConnectorNo auth
  • Search real student IELTS Writing answers scored by AI examiner. Args: task: IELTS Writing task number — 1 (reports/letters) or 2 (essays). band: whole band to filter on; matches half-bands too (8 -> 8.0-8.5). query: free-text match against the question/prompt. limit: max results (1-50). Each result links to a full page with the question, the student's answer, and criterion-by-criterion examiner feedback. Use get_model_answer for the full content, or compare_question to see the same prompt at other bands.
    ConnectorNo auth
  • Returns CANDIDATE FOUNDATIONAL PAPERS for a research topic — cheap retrieval only, no synthesis. Ranks papers by a blend of citation count (0.6 weight, captures importance) and semantic similarity to your topic (0.4 weight). Use this to bootstrap a literature survey or get a fast sense of the landscape. For a synthesized orientation report (key concepts, open problems, reading order), use the /field-guide skill which calls this tool internally. Does not require a Pro API key — no LLM calls are made.
    ConnectorNo auth
  • Fetch Yahoo Shopping homepage editorial cards, including title, link, category, and thumbnail. This is a buying-guide and deals feed, not product search; use yahoo_shopping_category for a section, yahoo_shopping_article for one guide, or yahoo_shopping_store for one retailer's offers.
    ConnectorNo auth
  • Fetch an xTiles guide/documentation document by its `xtiles://guide/...` URI. The same documents are also exposed as MCP resources — use this tool when your client cannot read resources directly. Before generating Markdown for any `*_from_markdown` tool, read `xtiles://guide/markdown/overview` (and `/canvas`, `/collections`, `/blocks`) to get the syntax. `xtiles://guide/markdown/design` holds the colours, styles, layout and tab colours created content takes.
    ConnectorOAuth
  • Fetch Yahoo Shopping homepage editorial cards, including title, link, category, and thumbnail. This is a buying-guide and deals feed, not product search; use yahoo_shopping_category for a section, yahoo_shopping_article for one guide, or yahoo_shopping_store for one retailer's offers.
    ConnectorNo auth
  • Create a tag for labelling memories. First run search-tag and reuse a fitting tag — create only when none fits, to avoid duplicates. Omit `project_id` for a PRIVATE tag (only yours); pass it for a SHARED tag of that project. If that project has writing guidelines from its team (search-projects reports `has_instruction: true`), confirm you have read them with get-project and pass `instruction_reviewed: true`. Returns the tag, including its id.
    ConnectorOAuth
  • Dry-run a scenario node 'payload' against its config class BEFORE writing it: reports unknown/misspelled properties and type mismatches, and returns the normalized JSON. Read-only — nothing is created or changed. Worth calling for any node type whose get_scenario_node_schema card says validation=NONE, because there the server accepts a broken payload silently and the node only misbehaves once a contact reaches it.
    ConnectorOAuth
  • Creates a Deep Research task for comprehensive, single-topic research with citations. USE THIS for analyst-grade reports, NOT for batch data enrichment. Use Parallel Search MCP for quick lookups. After calling, share the URL with the user and STOP. Do not poll or check results unless otherwise instructed. Multi-turn research: The response includes an interaction_id. To ask follow-up questions that build on prior research, pass that interaction_id as previous_interaction_id in a new call. The follow-up run inherits accumulated context, so queries like "How does this compare to X?" work without restating the original topic. Note: the first run must be completed before the follow-up can use its context.
    ConnectorOAuth
  • Load filing workflow for SEC/EDGAR metadata, 8-K events, 10-K/10-Q reports. REQUIRES get_database_schema then get_query_patterns to be called first (in that order). Call BEFORE writing SQL whenever the user asks about filing dates, filing activity, "who filed", "filed a form", filing frequency, SEC filings, EDGAR, 8-K events, 10-K/10-Q reports, proxy statements, or any query involving the sec_filings table (metadata - when/what type, not transaction detail). For insider transaction detail (shares, prices, cluster buying), use load_insider_workflow instead. Can be combined with other workflow tools.
    ConnectorNo auth
  • Load filing workflow for SEC/EDGAR metadata, 8-K events, 10-K/10-Q reports. REQUIRES get_database_schema then get_query_patterns to be called first (in that order). Call BEFORE writing SQL whenever the user asks about filing dates, filing activity, "who filed", "filed a form", filing frequency, SEC filings, EDGAR, 8-K events, 10-K/10-Q reports, proxy statements, or any query involving the sec_filings table (metadata - when/what type, not transaction detail). For insider transaction detail (shares, prices, cluster buying), use load_insider_workflow instead. Can be combined with other workflow tools.
    ConnectorNo auth
  • Use this when the user asks to consolidate, reflect on, or organize their memories, or when memory_status or a search result reports that consolidation is available. Checks out a batch of unconsolidated memories from the connected vault under a 15 minute lease and returns their texts plus server instructions for writing reflection entries. Follow the returned instructions to write the entries, then call commit_reflections with the batch_id. Nothing is modified until commit.
    ConnectorNo auth