Skip to main content
Glama
812,622 tools. Updated 2026-11-20 19:27

"A guide to writing a paper for an SCI-indexed journal" matching MCP tools:

  • Semantic search over Japan's official government white papers: the Ministry of Defense white paper (防衛白書) in both its 2025 edition (令和7年版) and 2026 edition (令和8年版), and METI's trade white paper (通商白書, 2025 edition). Use this when the user asks about Japanese defense policy, the Self-Defense Forces, Japan's security environment, defense budgets or procurement programs, the Japan-US alliance, how Tokyo officially describes China, North Korea or Russia, or about Japan's trade strategy, global supply chain resilience, economic security, overdependence and economic coercion, or China's industrial policy and its effect on trade. One query searches all of them at once, and every result is labelled with its paper name and edition year. Because both defense editions are indexed together, a single query can surface how the same topic is described in each year: the 2026 edition adds parts and chapters that did not exist before, while other passages carry over from the previous year with little or no change. Reading the returned excerpts side by side therefore shows both what changed and what stayed the same. This tool retrieves passages; it does not compute the differences for you. Queries may be in English or Japanese — English queries are automatically translated before retrieval against the Japanese corpus. Returns ranked excerpts with paper name, chapter, page numbers and a source URL suitable for citation. Scope: the 2025 and 2026 editions of the defense white paper and the 2025 edition of the trade white paper only. Not a source for breaking news, press conferences, statistical databases, export control regulations, tariff schedules, or documents from other ministries.
    ConnectorNo auth
  • Attempt to download PDF of a CrossRef paper. Args: paper_id: CrossRef DOI (e.g., '10.1038/nature12373'). save_path: Directory to save the PDF (default: './downloads'). Returns: str: Message indicating that direct PDF download is not supported. Note: CrossRef is a citation database and doesn't provide direct PDF downloads. Use the DOI to access the paper through the publisher's website.
    ConnectorNo auth
  • Permanently delete a MANUAL journal entry by id. Immediate and irreversible. Only works on manually-created entries (ids like `ent…`). Journal entries auto-generated from a source document (invoice, bill, income, expense — ids like `ent-1-inv…`, `ent-1-cont…`, `ent-1-exp…`) cannot be removed this way: delete the SOURCE document instead, and its journal entry is removed with it. Confirm with the user before deleting.
    Connector
    Destructive
    OAuth
  • 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
  • [JOURNAL] Void a mis-logged journal trade by trade_id (wrong asset, duplicate, fat-finger) with an optional reason. Soft-delete: the trade is removed from your stats and the default journal view but retained and recoverable (get_journal status='void' lists voided trades). Voiding a CLOSED trade removes its outcome from your calibration — disclosed in the response. Use this for entries that never should have existed; use close_trade for real trades that ended. Pro.
    Connector
    Destructive
    No auth
  • [JOURNAL] Void a mis-logged journal trade by trade_id (wrong asset, duplicate, fat-finger) with an optional reason. Soft-delete: the trade is removed from your stats and the default journal view but retained and recoverable (get_journal status='void' lists voided trades). Voiding a CLOSED trade removes its outcome from your calibration — disclosed in the response. Use this for entries that never should have existed; use close_trade for real trades that ended. Pro.
    Connector
    Destructive
    No auth

Matching MCP Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents to call tools through a security gateway that intercepts requests, enforces deterministic policy and risk checks, blocks or escalates high-risk actions for human approval, and keeps tool credentials and audit logs protected.
    1
    MIT

Matching MCP Connectors

  • Git AOAuth

    Many AI agents on one repo, every change lands on main. Read code, propose changes, review, read CI.

  • Indicative UK skip hire prices by town, council skip permit rules and skip size recommendations.

  • 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
  • Internal transfers produce NO transaction hash because no transaction occurs — this append-only journal is their only record. Never truncated; page with `before` (a seq number). Use this when a user asks to verify or dispute an internal payment, since there is no chain to check.
    ConnectorNo auth
  • 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
  • Record YOUR verdict on a paper — why it matters for your work, when to use it, or why you ruled it out. One note per paper, upserted (writing again replaces it), so it is safe to call repeatedly. Requires SF_API_KEY. WHY IT MATTERS: this note is the only thing that survives between sessions. list_library returns note_text on every saved paper, so a verdict written now is what a future session reads INSTEAD of re-reading the paper and re-deriving the same conclusion. WRITE A JUDGMENT, NOT A SUMMARY — the paper already carries llm_summary and an abstract, so restating what the paper says adds nothing. Write what those cannot: how it bears on YOUR problem. Prefer a claim someone could later prove wrong ("needs a labeled trace log we don't have", "our baseline — beat this on the 7B setting") over an unfalsifiable verdict ("interesting", "not very relevant"), because a mechanism can be re-checked when circumstances change and a sentiment cannot. State the basis when it is thin: a verdict formed from the abstract alone deserves "(abstract only)", since fetch_fulltext defaults to ~800 characters of the results section rather than the whole paper. Pass action='get' to read the existing note before overwriting it — worth doing when a prior session may already have judged this paper. To correct a note, just write the corrected text (it replaces).
    ConnectorNo auth
  • Replace a day note's text and/or move it to another day, by note id (from journal_get_day or journal_search_notes). The body is replaced whole — to append, read the current text first and send the full new version. Trade notes are edited with journal_update_trade, not here. Returns the updated note. Day notes in the LuxAlgo journal: https://docs.luxalgo.com/platform/workspaces/journal/notes Requires signing in with a LuxAlgo account (OAuth).
    Connector
    Destructive
    No auth
  • Search 130,000+ peer-reviewed sustainability papers and the account's uploads. Articles from Sustainability, the Journal of Cleaner Production, the International Journal of Life Cycle Assessment and the Journal of Industrial Ecology, 1993 to the present — LCA, material flows, energy, food and agriculture, materials, waste, buildings and policy. English-language; most entries are abstract and metadata only. Returns ref-numbered metadata only (title, authors, year, journal, DOI) — no abstract, no excerpts. Refs (e.g. `k1`, `k7`) persist for this session and are accepted by `knowledge_get_excerpts` (passages) and `knowledge_get_full_document` (the full paper). `limit` defaults to 12; a larger limit suits broad literature surveys. Optional filters: `journal` (its full name) and `year_from` / `year_to`.
    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
  • Fetch one paper: its summary, authors, venue, figures, linked resources, or full text. Accepts a Lacuna artifact ID or paper URL from search_lacuna, or an outside identifier for the same paper: an arXiv ID (2310.06825), a DOI, or an arXiv, DOI or OpenReview URL. Use this when the user names a specific paper or after a search. For an outside identifier that is not in Lacuna's ML/AI corpus, the result is `found: false` with a note saying so. The default view is a summary; ask for the full text only when the summary does not answer the question. include_resources adds linked resources (code repositories, datasets, models, and demos) in context and full views by default. Pass False to omit them; other views ignore this option. Pass a resource entry's id to get_resource for further details. view selects the response shape. `context` requests Lacuna's compact agent-oriented context by default, while the four single-field views (blog/figures/concepts/neighbors) return isolated sub-resources: - "context" (default, recommended): agent-oriented summary with summary_markdown, authors, and a small figure preview. Start here for almost everything. Available versions are included when present; to read another version, use its artifact ID from the returned version list. - "full": raw upstream paper record. Cheaper than context when you only need basic metadata. - "preview": compact card with unique fields `excerpt`, `excerpt_kind`, `bookmarked`. Use for citation-style display. - "blog": just the summary_markdown content, without the rest of the context envelope. - "figures": just the figures list. - "concepts": just the concepts list. - "neighbors": just the related-papers list. - "fulltext": the paper itself, `max_chars` at a time (default 40,000; 1,000 to 100,000, other values are moved into that range) from `offset`; pass the returned `next_offset` to keep reading. `total_chars` is the length of the whole text, and an `offset` past it returns empty text. `format` says what you got: "latex" is the arXiv LaTeX source without its bibliography (citations appear as \cite keys); "pdf_text" is text extracted from the PDF, where equations and tables can be garbled. Lacuna holds text for most arXiv papers and for fewer papers known only by DOI; a paper without text returns `available: false`. figure_limit (context view only) caps the figure preview (server default 3). Pass 0 to suppress figure previews while keeping a `figures_truncated` signal.
    ConnectorNo auth
  • List preprints that appeared as journal articles within a journal publication-date interval, each with its journal DOI, journal name, publication date, and preprint metadata — the same record biorxiv_get_published_version returns for one DOI. The dates filter on journal publication, not preprint posting, so most rows were posted months or years earlier; use biorxiv_list_recent for preprints posted in an interval. `publisher`, a journal DOI prefix such as 10.7554 for eLife, limits the listing to the bioRxiv preprints published under it; those rows carry no journal name, authors, or abstract, and a prefix api.biorxiv.org does not recognize raises invalid_publisher. Returns `limit` publications per server (default 25, up to 100 — the page api.biorxiv.org serves; a larger limit returns 100 and says so). Continue at the `nextCursor` a page returns rather than stepping `cursor` by a fixed amount; `limit: 100` walks an interval in the fewest calls. When server="both" (default), per-server pagination state is returned separately, since one cursor can be past the end of one server and inside the other — to continue a single server, pass its `nextCursor` with `server` set to that server. One server failing under server="both" does not abort the call: the other server's page is still returned and the failed one is named in `failed[]`. Every attempted server failing raises a retryable upstream_unavailable (or rate_limited) error rather than an empty page. Abstracts are omitted by default to keep the page small — pass include_abstract: true for the whole page. Every preprintDoi, 10.1101/ and 10.64898/ alike, is accepted by biorxiv_get_preprint and the other DOI tools.
    ConnectorNo auth
  • Read the full text of a paper in the user's own paper library (uploaded PDFs). Text is extracted and page-numbered ([Page N]). Use this to answer questions about a specific paper the user uploaded. Call search_my_papers first when you only know a topic/title, not the paper id. Long papers are truncated; re-call with start_page/end_page to continue reading.
    ConnectorAPI key
  • Start a strategy live: it runs on live market data, on paper, with a note on it every morning (the lab's paper trade). It is what "start it live, follow it, paper trade it, run it live, watch it" ask for, and what a tap on a run's offer to start it live does. save_trading_config never does this: it keeps a run's settings, and nothing goes live from it. A first call starts nothing: its answer carries `ask`, the question for the person, with two offers. The same call with confirm=true, made after the person's yes, starts it. What it tracks: a finished run of this account (task_id: a ready test, a paper's circuit, a saved lab project's run, a backtest or a walk-forward), a published paper (study, from search or fetch) or one of the person's saved lab projects (project_id, from list_my_primitives_projects). It registers the strategy in the person's saved work, sets it up on paper with 100,000 for 90 days, checks it on the last six months and puts it live. Its first update comes after the next US market close. When the check takes longer, it goes on on QuanterLab and the strategy goes live by itself when it is done. Nothing here places an order or moves money: it is simulated on paper, on the data served each day. An account runs one strategy at a time. With one already tracked, a call starts nothing and its `ask` offers the swap, with two offers. The same call with replace=true and the replace_id its message names, made after the person's yes, stops that one (its record is kept) and tracks this one instead. Its card shows what started; `message` and `open_url` say the same for a host without cards. A strategy that cannot go live as it is answers with why in `message`, and, for a paper whose data stops at its publication, an offer with the exact call of its live version. my_paper_trades says later how it is doing. Args: task_id: The task_id of one of this account's finished runs. study: Instead of task_id, a published paper's id. project_id: Instead of task_id, the id of one of the account's saved lab projects. live_version: With study, true tracks the paper's live version: the same rule on the data served today. replace: True once the person has said yes to tracking this one instead of the one the account tracks. replace_id: With replace, the id of the strategy the account tracks, as the answer that asked names it. Another one tracked by then is asked about again. confirm: True once the person has said yes to the question the first call asked.
    Connector
    Destructive
    OAuth
  • 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
  • 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