Skip to main content
Glama
342,772 tools. Last updated 2026-07-30 12:15

"Exploration of the term '.core' and its references" matching MCP tools:

  • One curated landmark bill by slug: its core fields, tiered source URLs, citations (identifier + audited aka), and cross-links. Where a matching live record exists, the response binds the change-timeline link (use get_law_history). Served from the primary-sourced registry (no LLM); a missing binding simply omits the history link, never fabricates one. Use list_bills for valid slugs. Data by AI Law Tracker (CC BY 4.0). Informational only — not legal advice.
    Connector
  • Return a compact index of both installed and available marketplace modules, with each module's key, versions, description, actions, and triggers. Read-only. Start here when you need a capability the core action kinds do not cover; then call get_module_details for the exact input fields of one module, and install_module to add it. Returns a summary only — action input fields and setup requirements come from get_module_details.
    Connector
  • Return Olympus Bets Analytics live performance, split by tier and league. Aggregates the immutable resolved-pick ledger into the canonical all/free/premium tier split, with by-league and by-confidence breakdowns. Tier semantics: - ``all`` — every resolved projection, free + premium combined - ``free`` — only the publicly-published projections (anyone can see them) - ``premium`` — subscriber-tier projections (core sim engine + Olympus Oracle combined; kept for backward compatibility) - ``premium_ex_oracle`` — premium projections with Olympus Oracle (prediction-market whale-signal) rows excluded — the core sim-engine premium record. Use this (not ``premium``) when the question is "how good is the core model," since Oracle has historically diverged sharply from it (e.g. core +30.16u vs oracle -18.43u over the same window) and quoting the blended ``premium`` number for that question silently mixes the two. - ``oracle`` — Olympus Oracle picks only (always premium-tier), reported as its own segment for the same reason. Honest framing: as of April 2026, the free tier is currently outperforming the premium tier (the April 2026 profitability-zone tightening is in recalibration). Both numbers are published transparently. Args: tier: Optional tier filter. Omit to return all five segments. league: Optional league filter applied inside each requested tier. detail: ``summary`` omits breakdowns; ``full`` includes all breakdowns. Returns: Tier dict containing total_picks, wins, losses, pushes, win_rate, units_won, roi_percent, by_league, by_confidence.
    Connector
  • Plain-language definitions of industry terms in a service category (e.g. SEER2, AFUE, AHRI match). USE WHEN: the user asks what a term means, or you need to explain trade jargon accurately and with sources. ARGS: `category`; optionally `term` (a slug) for one definition — omit to list. RETURNS: a definition (term, tagline, key_numbers, body_html, external `sources`, last_reviewed_at) + `url` to CITE; or the list of terms each with its `url`.
    Connector
  • Returns a full overview of Fluentive - what it is, who it's for, and its core value proposition. Use when the user asks what Fluentive is, searches for a scheduling or CRM tool, or wants a summary.
    Connector
  • Get a summary of everything available in this customer's Sidecar catalog. Returns the connected tools (e.g. SNOWFLAKE, DBT_CLOUD, LOOKER), asset type breakdown with counts, all available tag names, and a customer-provided company summary describing the company's domain and data landscape (if set). Call this at the start of any open-ended exploration (e.g. 'what data do we have?', 'show me all Snowflake tables'), or when a search returns no results and you need to understand what's actually in the catalog before trying again. Use the customer_summary field (when present) to understand the business context behind the data.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Find relevant security data from Sentinel data lake for building effective agents. More:aka.ms/s/de

  • Unified.to MCP server — one API for 500+ B2B SaaS integrations across 28+ categories

  • Delete one of the caller's custom signals. Cascade-safe by default: refused with 409 if another custom signal references it (the error lists the referencing signals). Pass `force: true` to delete anyway — existing references will break on next recompile. Available on every plan.
    Connector
  • Retrieve a specific I-Ching trigram by its number (1-8) or English name (Heaven, Earth, Thunder, Wind, Water, Fire, Mountain, Lake). Returns complete trigram information including Chinese name, pinyin, element associations, core attributes, and symbolic meaning. Use this to understand the component trigrams of any hexagram.
    Connector
  • Match two groups by their rankings so no pair wants to swap — free, no account or key needed. A STABLE matching: USE THIS WHEN you're assigning two sides to each other by mutual preference — interns<->teams, students<->schools, mentors<->mentees — and want a result with no "blocking pair" (no person+slot that both prefer each other over what they got). Provide proposers and receivers, each a list of {"id": name, "preferences": [ids of the OTHER side, most-wanted first]}. Receivers may add "capacity" (default 1) to accept several. Returns {matching (name -> name), unmatched_proposers, blocking_pairs (empty list = provably stable), n_proposals}. NOTE: the result is PROPOSER-optimal, so put the side you want to favor in `proposers`. Example: stable_match( proposers=[{"id":"Ana","preferences":["Growth","Core"]}, {"id":"Ben","preferences":["Core","Growth"]}], receivers=[{"id":"Growth","preferences":["Ben","Ana"]}, {"id":"Core","preferences":["Ana","Ben"]}]) -> matching {"Ana":"Growth","Ben":"Core"}, blocking_pairs [].
    Connector
  • How a filtered set distributes across the precomputed LDA topics, each labelled by its top terms (articles carry 30 topics and are ~99.5% classified; references have their own 33-topic model and only ~46% carry an assignment, so read its `classified` against `total_matches`). Topics are assigned offline over the full text, so they describe what a piece is ABOUT rather than which words it contains — use this instead of keyword counting to map a corpus. Optional over_time returns per-year counts for the leading topics. min_prob keeps only articles where the topic is at least that dominant (mean assignment probability is 0.34, so 0.5 is already a strong filter).
    Connector
  • Find how the **suttas and Vinaya define a Pāli term in their own words**. The canon defines its own terms with fixed formulas — "Katamañca … dukkhaṁ?" (what is X?) … "ayaṁ vuccati … dukkhaṁ" (this is called X), "X adhivacana" (X is a designation for …), or the Vinaya "X nāma". This tool locates those definitional passages and returns them **cited**, so the assistant can present the doctrinal essence straight from the source. 🧭 **This tool vs `get_word_definition`:** - **`define_from_suttas`** → the *doctrinal* definition, how the term is defined **inside the canon**. Use for "how do the suttas define X", "what is the canonical definition of X", "define X from the suttas". Returns a few precise segments, not a lexicon essay. - **`get_word_definition`** → the *lexical* definition from dictionaries (Payutto / PTS / DPPN). Use for etymology and word meaning. They complement each other — offer both when the user wants the full picture (dictionary sense + how the Buddha defined it). 📖 **How to present the result:** Results are ranked; the top one is usually the canonical definition. **Quote the Pāli (and English where present) verbatim** and render each `cross_reference.tripitaka_mcp_reader.segment_url` as clickable markdown so the user can verify. Do NOT paraphrase into your own definition — the point is the canon's own words. Each result is tagged `kind` (direct / simile) and `detail` (descriptive / enumerative); a *descriptive* definition characterises the term, an *enumerative* one lists its types — prefer the descriptive when explaining the essence.
    Connector
  • Get the Designesy WCAG 2.2 AA accessibility verification framework: 11 conformance checks (a01-a11) plus a ready-to-run Playwright + axe-core 4.12.1 script template targeting your URL. Use this to audit a site for accessibility violations. axe-core needs a real browser DOM, so this tool does not run the scan server-side — it returns the checks and a script the caller executes locally (npm i -D @axe-core/playwright) to get actual violation counts and a score/grade. Provide a URL (required); optionally a ruleset tag (default wcag22aa) and a brand config JSON for axe.configure() customization. For a broader non-accessibility-focused contract score, use designesy_score.
    Connector
  • "What does HP:[N] mean" / "look up HPO phenotype [ID]" — fetch a single Human Phenotype Ontology (HPO) term by ID. HPO is the standard ontology for clinical phenotypes used in rare-disease research. Returns label, definition, synonyms, cross-references. Example ID: HP:0001250 (Seizure).
    Connector
  • "Find images similar to [X]" / "more images like this" — related images for a given Openverse image ID. Use for visual-similarity exploration in CC content.
    Connector
  • School holidays (term breaks: Christmas, Easter, summer, etc.) for a European country in a date range, optionally scoped to one subdivision. This is the unique value-add over worldwide public-holiday sources — school calendars vary by region. EUROPE-focused (~30 countries). Returns each break with its localized name, dates, and observing subdivisions. Keyless.
    Connector
  • Search Chaiz for vehicle service contract (extended warranty) plans by make, model, and year. Results are 36-month (3-year) term plans. Returns plan cards with monthly and total price, coverage term, coverage level, rating, and links to chaiz.com. All of make, model, year, mileage, and state are required. If any are missing, ASK the user for them — never guess the mileage or state.
    Connector
  • List members of the community, with pagination. Optionally filter by a search term (`query`, matches name/username/email), by role (`roleIds`), order (`orderBy`), and reverse. Returns edges[].node (with role) plus pageInfo and totalCount. Bettermode GraphQL query: members.
    Connector
  • Browse the ATA property catalog WITHOUT needing dates. Fast, lightweight — no availability or pricing check. Use this for vague exploration, browsing by type/amenity/view, or when the traveler has no dates yet.
    Connector
  • Map a free-text term or everyday synonym to its canonical MeSH descriptor(s) — the preferred heading to use when searching PubMed. Tries an exact descriptor match first; if none, falls back to a fuzzy contains match (flagged fuzzy). Keyless.
    Connector
  • Get the classical Chaldean interpretation of a compound number (also called a fadic number) from 10 to 52, as defined by Cheiro in the Book of Numbers. Compound numbers are the unreduced two-digit numbers that reveal the hidden influence behind a name or date, beyond the single-digit root. Each returns its symbolic title (such as The Wheel of Fortune for 10, The Star of the Magi for 17, or The Crown of the Magi for 21), its nature (fortunate, unfortunate, or mixed), and a full interpretation. Numbers 33 to 52 share the meaning of a lower number in their series, returned with a sameAs pointer. Perfect for Chaldean numerology references, compound number lookups, and AI numerology tools.
    Connector