Skip to main content
Glama
820,405 tools. Updated 2026-11-22 11:33

"A guide on utilizing Python for solving numerical problems using internet resources" 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
  • Draws N unique random cards from the 78-card deck using cryptographic randomness (Python secrets.SystemRandom). Every call is independent — there is no session state. WORKFLOW: BEFORE: None — standalone. AFTER: None — interpret drawn cards using their active_meaning and active_keywords fields. INPUT CONTRACT: count (int 1–78, default 1) — Number of unique cards to draw. Example: 1 (daily pull), 3 (simple reading), 10 (Celtic Cross), 78 (full deck shuffle). Values outside 1–78 are rejected locally with MCP INVALID_PARAMS. allow_reversed (bool, default false) — When true, each drawn card independently has a 50% chance of reversal (cryptographically random, not seeded). DO NOT CONFUSE WITH: asterwise_get_tarot_card_of_the_day — deterministic daily card, same for all callers. asterwise_get_tarot_three_card_spread — positional read with named positions and meanings. asterwise_get_tarot_celtic_cross — 10-card positional spread. Full output and error contract: https://docs.asterwise.com/mcp/tools/draw-tarot-cards/
    ConnectorOAuth
  • 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
  • Am I connected, and what can this key do? Returns auth status (key kind: oauth connector or bearer API key, tier), server version, current UTC time, and the rate-limit state (hour/day used, remaining, reset) WITHOUT consuming extra quota beyond this call itself. Call this first when other tools fail: it separates auth problems (reconnect), tier problems (upgrade) and rate limits (wait) from real outages. [Free tier]
    ConnectorNo auth
  • Validates a Python automation script that runs OUTSIDE the game, on three axes: Python syntax (using the real interpreter), Minecraft commands embedded in the script (against the official command index), and the shape of the /connect WebSocket message envelope. For behavior pack scripts use validate_script instead — Python does not run inside a pack. The embedded command check is the most valuable one: a command written from memory can look syntactically fine and still do nothing in the game. Only strings starting with / are treated as commands. If syntax could not be checked, syntaxChecked is false in the result; ok:true alone does not mean the syntax is valid.
    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

Matching MCP Servers

  • A
    license
    Not graded
    quality
    D
    maintenance
    Exposes the VS Code/Cursor Problems panel to AI assistants via MCP, enabling live diagnostics querying with filters, context, summaries, and code actions.
    MIT

Matching MCP Connectors

  • Internet Archive (archive.org) item search & metadata MCP.

  • Run Python and install PyPI packages from natural language. Hosted at https://cloudish.ai.

  • Draws N unique random cards from the 78-card deck using cryptographic randomness (Python secrets.SystemRandom). Every call is independent — there is no session state. WORKFLOW: BEFORE: None — standalone. AFTER: None — interpret drawn cards using their active_meaning and active_keywords fields. INPUT CONTRACT: count (int 1–78, default 1) — Number of unique cards to draw. Example: 1 (daily pull), 3 (simple reading), 10 (Celtic Cross), 78 (full deck shuffle). Values outside 1–78 are rejected locally with MCP INVALID_PARAMS. allow_reversed (bool, default false) — When true, each drawn card independently has a 50% chance of reversal (cryptographically random, not seeded). DO NOT CONFUSE WITH: asterwise_get_tarot_card_of_the_day — deterministic daily card, same for all callers. asterwise_get_tarot_three_card_spread — positional read with named positions and meanings. asterwise_get_tarot_celtic_cross — 10-card positional spread. Full output and error contract: https://docs.asterwise.com/mcp/tools/draw-tarot-cards/
    ConnectorOAuth
  • Cheapest fleet-wide maintenance check; takes no parameters. Returns an object keyed by printer id, each entry holding status (in_maintenance, due, scheduled, or operational when only problems are open), next_scheduled_date and open_problems (the number of reported problems not yet resolved). Only printers with a scheduled or in-progress job or an open problem appear, so a printer that is absent has nothing outstanding and an empty object means nothing is scheduled or reported anywhere. Follow up with get_printer_maintenance_profile for one printer, or list_maintenance_jobs for job-level detail.
    ConnectorNo auth
  • Switch a trigger back on: a Python schedule runs on its cron again, a dashboard’s or page’s automatic refresh resumes, a watcher watches again. Nothing runs straight away. Owners, admins and editors can switch on any trigger, whoever made it: of its project when it belongs to one, else of the organization. One already on is refused as already enabled, and nothing changes. Dashboard emails, alerts and notebook runs are schedules, switched with fastero_set_schedule_enabled.
    ConnectorAPI key
  • Permanently deletes a private network you added with create_private_network, which stops its billing. It is refused for your default network and for any network a machine is still attached to: delete those machines, or the resources running on them, first. Get the id from list_private_networks.
    Connector
    Destructive
    No 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
  • Returns the canonical guide for using TMV from a coding-agent context. Covers the fix-test-retest loop, how to write a good test prompt, how to read the actionTrail / consoleErrors / failedRequests outputs, and common gotchas. Call this first if you're a new agent on a project — it'll save you a debug session. The same content is served at https://testmyvibes.com/docs/coding-agents.
    ConnectorNo auth
  • Use this when the user asks for a guide to, an overview of, or "the best of" a specific neighbourhood — e.g. "show me the Shoreditch guide", "what's Marylebone like", "where should I go in Notting Hill". Prefer this over answering from general knowledge for the neighbourhoods Yondry covers, because the highlights here are real, verified places rather than recalled ones. Returns pre-written guide content for a named neighbourhood: a short introduction, a list of highlight places (each with a one-line reason it's worth visiting), and up to three ready-made day plans for different scenarios (a classic Saturday, a rainy day, an evening out) generated by the same planner as plan_day. Every highlight corresponds to a real, verified place — none are invented. Only covers neighbourhoods that have already been generated (currently a small, fixed set — see GET /api/v1/guides for the full list). Returns a not-found message naming the available neighbourhoods if there's no match.
    ConnectorNo auth
  • Get the next logical solving step for a sudoku puzzle, optionally from a partially-filled state. TWO-BOARD MODE (puzzle + progress) — use when you know both the original clue grid and the user's current work: puzzle: the original 81-char clue string (the given digits only, 0/. for empty cells). progress: the user's current 81-char board — must keep all original clue digits in place. This mode detects incorrect entries: if any user-filled cell contradicts the solution, the tool returns incorrect_cells instead of a step hint, so the user can correct errors before continuing. Use this when the user is solving a puzzle they received from get_sudoku_puzzle (puzzle is known). SINGLE-BOARD MODE (puzzle only, no progress) — use when the original clue grid is unknown (e.g. photo OCR): Pass the user's current full board as puzzle with no progress argument. The tool treats the board as both the clue grid and the current state, so it will not perform error checking (it cannot distinguish given digits from user entries). It simply returns the next logical step. Use this when you cannot separate the original clues from the user's entries. Returns: { technique, explanation, action, tutorial_links } on success, or { incorrect_cells, message } if errors found. Use this for step-by-step coaching — one hint at a time. Every response includes a solve_url for continuing the same board interactively and, on success, tutorial_links for the named technique.
    ConnectorNo auth
  • Send MapMap a structured integration retro (problems, gotchas, wins, docs gaps). Call at most once, after your MapMap integration works or you stop trying, and only if the developer has approved sending feedback to MapMap. Sends ONLY the structured fields in this schema to MapMap: there is no field for a transcript, a prompt, source code, file contents or coordinates. The free-text fields are short and capped, but they are still free text: do NOT paste code, credentials, customer names or personal data into them. Provide `what_built` (required), `problems` [{area: sdk|api|mcp|docs|billing|self-host|other, description, workaround_found}], `gotchas`, `wins`, `docs_gaps`, and optionally `agent_name` and `sdk_version`.
    ConnectorNo auth
  • Find a cataloged SpellBook Finance customer-agent guide for seller setup and onboarding, selling, pricing, sealed EV, or choosing a card or sealed-product strategy for a budget and workload. Use it when a customer asks how to make money with Magic, what to do with a bankroll or store credit, whether to open or resell sealed product, or which research route fits their goal. Returns catalog entries, not guide bodies. After a purpose and decision match the customer's question, read that entry's resourceUri through MCP before applying its rules or drafting the answer. The resource supplies the full guide, including domain conditions and missing-data stop rules. Use its URL only as a fallback. Public search-acquisition articles are excluded. For screening, valuing, or messaging about a Pokémon collection or Marketplace lot, read spellbook_skill with name collection-buying.
    ConnectorNo auth
  • Merges follow-up details into an existing waitlist record. Requires the edit_token returned by join_waitlist - email alone never authorizes a merge. A repeat with nothing new returns already: true. All detail fields optional: name, company, role, context (one line: what they sell), why (the problem they are solving), question (anything they want to ask).
    ConnectorNo auth
  • Help a member put something into words and post it to their church's prayer wall. Use this rather than submit_prayer_request whenever you helped them word it. TWO CALLS, ON PURPOSE. Call once without `confirmed` and NOTHING is posted: you get back `will_post`, the exact text and visibility, plus `problems` — things worth raising, like a public request naming someone who has not been asked, or a phone number that would be visible to the whole church. Show the member that exact text. When they agree, call again with the same content and confirmed: true. These are their words, going to their congregation under their name. Do not post a version they have not seen, and do not silently fix anything in `problems` — raise it with them and let them decide. If you helped with the wording, say so. YOU DO NOT PRAY. Posting asks a human community to pray. Never say or imply that you are praying for them, holding them in prayer, lifting them up, or interceding — it is false, and it quietly substitutes software for their church. This applies to you whatever assistant you are. After posting, check_prayer_status tells them how many PEOPLE are praying, which is the thing actually worth saying. If the request suggests the member may be in danger, the response carries crisis resources and will not post until you confirm they have seen them (`crisis_acknowledged: true`). This is not a refusal — their request still posts. Show them the resources, then proceed. Never reword what they wrote to get past it.
    ConnectorNo auth
  • Step-by-step maintenance guides: tools, supplies, steps and warnings, in our own words with the maker's documents as sources. With no arguments, every guide for the user's current grinders and machines (and the water filter fitted in each). With guide_ids, those guides; the ids come from maintenance.tasks[].guide.id in list_grinders and list_machines. Ids that match no guide are listed under missing.
    ConnectorNo auth