Skip to main content
Glama
811,921 tools. Updated 2026-11-20 17:04

"A search for teaching and education resources" matching MCP tools:

  • Fetch the full content for one id returned by `search`: a rental listing (rental:<uuid>), a plan set (plan:<uuid>) or a published page (page:<route>). Returns {id, title, text, url, metadata}. Always cite the url. Hosts that can call specific tools should prefer get_rental or the resources.
    ConnectorNo auth
  • Run the classic operations-research teaching demo: pooled queueing (one shared queue, c servers) vs separate queues (c independent queues, one server each, λ/c traffic to each). Both runs have identical total capacity (c × μ) and identical total arrivals (λ), so the offered load ρ is the same; the only structural difference is whether arrivals share a queue or split into c isolated streams. The pooled configuration ALWAYS produces shorter waits — that's the whole teaching point. Use this when the user asks 'should we pool our resources?' / 'should we cross-train?' / 'why do banks have one line instead of c?' / 'what's the cost of siloing my call center into specialist queues?'. Returns both runs side by side with the pooled-vs-separate wait delta. ANTI-FABRICATION: numbers come from two real DES runs. Quote them VERBATIM.
    ConnectorNo auth
  • Vaaya's consultant. Describe ANY external capability you or the user might want — generate an image/video, search or scrape the web, run code in a sandbox, send/receive email, enrich a contact — and it helps figure out the best way, teaching the user what Vaaya can do. It is CONVERSATIONAL and remembers prior turns. It returns: mode='converse' (a reply to RELAY to the user verbatim — questions, options, ideas; get the user's response and call consult again with it, so the conversation continues), mode='call' (an ordered list of calls to run via `use`, with a message explaining the preferred choice + alternatives + why; multi-step results may contain placeholders like '<from step 1: sandbox_id>' — run earlier steps first and substitute), or mode='unsupported'. Every reply includes `suggestions` (2-3 things to do next) — surface these to the user. AFTER you run a `call` result's calls via `use`, call consult ONE more time with a short note on the outcome (what was produced / any failures) — it returns result-aware, Vaaya-grounded next steps to offer the user (the `call` result's `after_running` field reminds you). Call consult whenever you hit a capability gap or the user wants to know what's possible. It does NOT execute or bill — you run returned calls via `use`. ALWAYS show the user consult's `message` and `suggestions` and let them steer.
    ConnectorNo auth
  • Exhaustively survey the WHOLE Tipiṭaka for a term — guaranteed complete. Use this (not `search_by_keyword`) when the question is about **coverage or counting** rather than "show me the best passages": - "How many times does Kusinārā appear in the canon?" - "Every place ānāpānassati is mentioned — don't miss any" - "Which pitakas/how many suttas mention this term?" Unlike `search_by_keyword` (ranked, capped at 50, no total), this returns an **exact count**, a **per-pitaka breakdown**, the **distinct surface forms** that matched (so you can audit and discard over-matches), and a paginated enumeration. The `lexical` result carries `complete: true` — a hard guarantee that nothing was dropped for the chosen `match_scope`. Two layers, two different promises: - **lexical** — the word and its forms. Deterministic + EXHAUSTIVE. - **semantic** (`mode="thorough"`, hosted only) — passages teaching the same concept with DIFFERENT vocabulary (e.g. ānāpānassati via `assasati`/`passasati`). Approximate, **NOT exhaustive** — it never claims completeness, it only boosts recall.
    ConnectorNo auth
  • Return the safely validated redirect chain. Use only for public HTTP(S) resources; it does not execute JavaScript or bypass access controls. Pass url as an absolute public HTTP(S) URL. Keep fresh=false to allow cache reuse; set fresh=true only when a new upstream fetch is required.
    ConnectorNo auth
  • Classify MIME type, charset and bounded content length. Use only for public HTTP(S) resources; it does not execute JavaScript or bypass access controls. Pass url as an absolute public HTTP(S) URL. Keep fresh=false to allow cache reuse; set fresh=true only when a new upstream fetch is required.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents to generate teaching materials such as PPTs, handouts, lecture scripts, mind maps, teaching video storyboards, and Manim math animations, plus run quality checks and language normalization through 15 MCP tools.
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    MCP server for education statistics of the Canton and City of Zurich (BISTA), providing tools to query pupil numbers, school district trends, secondary school profiles, nationality breakdowns, and gymnasium graduation rates.
    8
    43 PyPI
    MIT

Matching MCP Connectors

  • List up to 100 image references without downloading images. Use only for public HTTP(S) resources; it does not execute JavaScript or bypass access controls. Pass url as an absolute public HTTP(S) URL. Keep fresh=false to allow cache reuse; set fresh=true only when a new upstream fetch is required.
    ConnectorNo auth
  • Discover up to five sitemap links declared by the requested page. Use only for public HTTP(S) resources; it does not execute JavaScript or bypass access controls. Pass url as an absolute public HTTP(S) URL. Keep fresh=false to allow cache reuse; set fresh=true only when a new upstream fetch is required.
    ConnectorNo auth
  • Maps only stable Tier1 finding identifiers to approved Tier1 services and public resources. Call after a Tier1 score or email-domain check. Do not submit prose, URLs, customer information, or invented identifiers. This tool performs no arbitrary fetching, makes no contact request, changes nothing, and stores nothing.
    ConnectorNo auth
  • Return safe network timing, payload and cacheability diagnostics. Use only for public HTTP(S) resources; it does not execute JavaScript or bypass access controls. Pass url as an absolute public HTTP(S) URL. Keep fresh=false to allow cache reuse; set fresh=true only when a new upstream fetch is required.
    ConnectorNo auth
  • Fetch a LIVE Amazon search-results page (SERP) right now — the ranked organic + sponsored listings a shopper would see this minute for a query, with position, ASIN, title, price, rating and badges. Use when the user wants CURRENT ranking/visibility: 'who ranks for "dog bed" on Amazon right now', 'is my ASIN on page 1 for this keyword', 'what's sponsored vs organic for this search'. This is a real-time fetch (takes ~10-40 seconds) — for warehouse keyword search use search_products; for buying advice use shopping_search. Amazon marketplaces only; up to 3 pages per call.
    ConnectorNo auth
  • Return the connected organization, the credential in use, and the granted workspace + environment ("TEST" or "PRODUCTION") targets — exactly the values the required workspaceId/environment arguments on targeted tools accept. Always available; call this first, and again whenever a tool returns UNAUTHORIZED or NOT_FOUND unexpectedly, or after this connection's access changes — resources live per-workspace.
    ConnectorOAuth
  • Browse Statistics Estonia's (Statistikaamet) statistics database tree by path. Top-level databases: keskkond (environment), majandus (economy), rahvastik (population: migration, births/deaths, family), sotsiaalelu (social life: labour market, education, health), eri-valdkondade-statistika (multidomain statistics), rahvaloendus (population and housing census), Lepetatud_tabelid (discontinued datasets). Returns child nodes (subcategories, type=l) or table descriptors at leaf nodes (type=t). Use empty path '' to get the top-level databases. Navigate hierarchically until type=t nodes appear, then use estonia-statistics.table_metadata. Data: andmed.stat.ee (PXWeb API), no auth required.
    ConnectorNo auth
  • Use this when the user asks how visible their product results are in Google web Search, and which product pages carry them. Search Console performance for one search appearance, defaulting to MERCHANT_LISTINGS: the appearance inventory of the property, a daily clicks / impressions / CTR / position timeline in date order, and the top pages (product URLs) behind it; appearances and pages are sorted by clicks, highest first, and CTR is a 0-100 percentage. Search Console merchant listings counts enriched product results in web Search only, so it does not reconcile to one figure with Merchant Center free listings. Not for the Shopping tab, Images, Lens, YouTube or Maps: use get_organic_shopping_performance. Always served from the live Search Console API: search appearance is never stored in the GSC Wizard warehouse, and it can be filtered on but never grouped with another dimension. `hasAppearance` is false when the property has no rows for the requested appearance, and `emptyBecause` is set whenever it has no impressions, which is normal for non-ecommerce sites. The window may span at most 16 months (Search Console retention); a longer one is rejected with bad_request. Date range is optional: omit startDate/endDate to analyze the last 28 settled days (data lags ~2-3 days).
    ConnectorOAuth
  • 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
  • Get ceiling rate benchmarks for IGCE development. Returns statistical summary for a labor category: count, min, max, avg, median, standard deviation, percentile distribution (P10-P90), education breakdown, worksite counts (worksite_breakdown: Customer_Facility / Contractor_Facility / Virtual; counts only, prices are pooled across sites), and outlier bounds. GSA's keyword search matches labor_category, vendor_name and idv_piid. The returned statistics pool all matching rate rows, including unrelated labor titles when a vendor name or contract number matches the phrase. Check population_scope and matched_titles before using the statistics. off_title_matches_detected flags observed titles that do not match the requested phrase; title_only_population_verified is false when the title aggregation is missing, empty, truncated or approximate. A title containing the phrase is not necessarily the exact grade: 'Registered Nurse I' also matches Nurse II, III and IV. Check exact_title_population_verified, exact_title_rate_count and non_exact_title_examples before treating a pool as that specific title. For title-only rates, call suggest_contains on labor_category to discover an exact title, then exact_search on labor_category. Different spellings remain separate searches ('Cyber Security Analyst' vs 'Cybersecurity Analyst'). Statistics are on current-year ceiling rates (current_price), not next-year or option-year prices. These are not-to-exceed ceiling rates, not prices paid. Ceiling-rate comparisons alone do not establish a proposed price's reasonableness. Optional filters: education_level, experience_min/max, business_size ('S' or 'O'), sin (e.g. '541611'), security_clearance ('yes' or 'no').
    ConnectorNo auth
  • Use this when the user wants a word search puzzle (word find, word search maker, printable word search for kids or a class) from a list of words. Accepts 5-40 words for a letter grid: right and down for easy, adding diagonals for medium, all 8 directions including backwards for hard; checks placed words for duplicate occurrences and reports words left out. Shows a playable puzzle and returns a printable PDF with an answer key. Not for crosswords (use generate_crossword) and does not find words in a grid the user already has.
    ConnectorNo auth
  • Reads rows from one Google Ads resource. The tool writes the GAQL query from these parameters: SELECT `fields` FROM `resource` WHERE `conditions` (joined with AND) ORDER BY `orderings` LIMIT `limit`. Args: customer_id: The customer ID, digits only (123-456-7890 is 1234567890). fields: The fields to return, each written in full, e.g. "campaign.id". resource: The one resource the rows come from, e.g. "campaign". conditions: Filters, one GAQL condition each, e.g. "campaign.id = 123"; every one must hold. orderings: Sort order, e.g. "metrics.clicks DESC". limit: The maximum number of rows to return. start_date: Report start date (YYYY-MM-DD). Adds a quoted `segments.date` filter — use this instead of hand-writing dates into `conditions`. On change_event/change_status it filters their own date-time. end_date: Report end date (YYYY-MM-DD). Combined with start_date this produces a finite `segments.date BETWEEN 'start' AND 'end'` filter (on change_event/change_status, a range on their own date-time instead). There is no parameter for a whole query string, and a parameter not listed above is refused rather than ignored. ### Example The enabled ads of one campaign, by ad group: resource="ad_group_ad" fields=["ad_group.name", "ad_group_ad.ad.id", "ad_group_ad.status"] conditions=["campaign.id = 12345678901", "ad_group_ad.status = 'ENABLED'"] orderings=["ad_group.name"] Clicks and cost by campaign for August: resource="campaign" fields=["campaign.name", "metrics.clicks", "metrics.cost_micros"] start_date="2026-08-01", end_date="2026-08-31" ### GAQL reference, for writing fields and conditions Overview: https://developers.google.com/google-ads/api/docs/query/overview Language Grammar: https://developers.google.com/google-ads/api/docs/query/grammar Resources and fields: https://developers.google.com/google-ads/api/fields/v23/overview get_resource_metadata returns the fields a resource can select, filter and sort by, and the list of valid resources when the name given is not one. Field names are written in full ('campaign.id', not 'id'); wildcards and partial field names are not accepted. Common resources: campaign, ad_group, ad_group_ad, ad_group_criterion, keyword_view, search_term_view, campaign_budget, customer, asset, change_event. ### Dates start_date and end_date (YYYY-MM-DD) add a correctly quoted `segments.date` filter (change_event and change_status are the exception, see below), which avoids the most common query error. A date written into `conditions` is a quoted string, e.g. segments.date BETWEEN '2026-08-01' AND '2026-08-28' (an unquoted date is a GAQL syntax error). Date literals from the Grammar (e.g. DURING LAST_7_DAYS) are not supported here. ### Keyword and search-term reporting Metrics on keyword_view and search_term_view are attributed only to the matched keyword/term, so they will NOT sum to the campaign or ad_group totals. The remainder is traffic with no single matched keyword, plus low-volume search terms Google withholds below a privacy threshold. This is expected Google attribution, NOT a data error; top-line numbers reconcile at the campaign or ad level. ### change_event and change_status Pass start_date AND end_date plus a limit of at most 10000. The dates filter change_event.change_date_time / change_status.last_change_date_time (these resources forbid segments.date). Google keeps change_event for the last 30 days and change_status for the last 90 days. ### Conversions Upload issues: offline_conversion_upload_conversion_action_summary (https://developers.google.com/google-ads/api/docs/conversions/upload-summaries). Tools revision: 7a2c68c7.
    ConnectorOAuth
  • App-only search behind the @ mention picker in the ChatGPT composer: given the typed text, it returns up to 20 of the user's notes and resources as linko://note/{id} and linko://resource/{id} links with title and excerpt. The host reads a link as Markdown only when the user picks it, so nothing is shared until then. It is not a general search; search_notes, search_resources and search serve assistants answering questions.
    ConnectorOAuth
  • Delete ONE AI package resource of a video in one language (eBook, mind map or quiz) — cannot be undone: its content, PDF, images and the published file are removed, also for legacy resources. Same as the dashboard's Remove. Refused while it is still generating (checked before deleting; if that check fails nothing is deleted). Other languages and resources stay. To remove a failed generation card use panda_delete_ai_workflow.
    Connector
    Destructive
    No auth
  • List every status page of the organization, newest first, in one unpaginated response: each page's UID, slug, name, default flag, enabled flag and visibility, without its sections. Takes no parameters. Use get_status_page with the UID or slug for one page's sections, resources or published incidents. Read-only: works with mcp:read tokens.
    ConnectorAPI key