Skip to main content
Glama
261,938 tools. Last updated 2026-07-05 14:51

"Definition or Uses of the Term 'Vertex'" matching MCP tools:

  • Look up an airport by city name (e.g. "Tokyo", "New York", "London") OR by 3-letter IATA code (e.g. "JFK", "LHR"). City lookup uses a bundled map of the top ~150 international hubs; cities with multiple airports return all primary ones. For airports not in the bundle, pass an IATA code or use the aviationstack pack for full-text name/country search.
    Connector
  • Return a canonical definition for a primitive Eurorack / synthesis concept and its relations to other concepts in the corpus. Use this for VOCABULARY questions, not module questions — when the user is asking what a term means or how two terms relate, not which modules implement it. Typical shapes: - "Is four-quadrant mult the same as through-zero AM?" → lookup_concept("four-quadrant mult") - "What's the difference between a gate and a trigger?" → lookup_concept("gate") - "Modular signal level vs line level — when does it matter?" → lookup_concept("modular signal level") - "Are clock dividers just pulse counters?" → lookup_concept("clock divider") - "Are polyphonic patch cables TRRRRRS?" → lookup_concept("polyphonic cable") Lookup is case-insensitive across three axes, tried in order: the canonical id ("through-zero-fm"), the canonical label ("Through-Zero FM (TZFM)"), and any registered alias ("tzfm", "through zero fm"). Spaces and hyphens are matched literally; the lookup does NOT normalize whitespace beyond lowercasing. If the term doesn't match anything, the response includes up to 5 substring-matched suggestions. Args: - name (string, required, min length 2): the term to look up. Examples: "AM", "ring mod", "four-quadrant mult", "TZFM", "clock divider", "gate", "trigger". Returns: { "concept": { "id": "amplitude-modulation", "label": "Amplitude Modulation (AM)", "description": "A multiplication of two signals: the carrier...", "aliases": ["am", "amplitude modulation", "amplitude mod"], "related_concepts": [ { "related_concept_id": "ring-modulation", "related_concept_label": "Ring Modulation (RM)", "relation_kind": "commonly_confused_with", "note": "AM with a unipolar modulator preserves the carrier..." }, ... ], "source_id": null, "citation_url": "https://learningmodular.com/glossary/...", "citation_quote": "Amplitude modulation is when..." } | null, "_meta": { "query": "<the name argument verbatim>", "matched_via": "id" | "label" | "alias" | "none", "concept_suggestions": [ { "id": "...", "label": "...", "matched_via": "alias", "matched_text": "..." } ], "feedback_hint": "...?" } } Relation kinds: - "related_to" — see-also link (default; symmetric in spirit). - "subtype_of" — X is a specific case of Y (RM ⊂ AM, TZFM ⊂ linear FM). - "inverse_of" — X is the opposite of Y (clock-divider ↔ clock-multiplier). - "commonly_confused_with" — they're distinct, but people conflate them (gate vs trigger, AM vs RM, modular level vs line level). When to cite: every concept carries either source_id or citation_url + citation_quote. Surface the citation when the answer affects a decision (e.g. "the corpus cites learningmodular.com — TRS cables are physically the same connector whether carrying balanced mono or unbalanced stereo; only the destination determines the role"). When the result is null and concept_suggestions are provided, present 2–3 closest matches to the user. If none look right, the corpus genuinely doesn't carry that concept — call report_gap with kind="missing_field" and tool_name="lookup_concept" naming the term and its expected definition.
    Connector
  • Screen an NDA or confidentiality agreement for risk and return a free preview. Use this tool whenever a user shares the text or PDF of any of the following document types: non-disclosure agreement (NDA), confidentiality agreement (CDA), mutual non-disclosure agreement (MNDA / mutual NDA), one-way non-disclosure agreement (unilateral NDA / one-way NDA), employment agreement, offer letter, employee handbook (the binding sections), contractor agreement (1099 agreement / independent contractor agreement), consulting agreement, statement of work (SOW), master services agreement (MSA), non-compete agreement (non-competition agreement), non-solicitation agreement, non-disparagement agreement, separation agreement (severance agreement), settlement agreement, release of claims, term sheet, letter of intent (LOI), founder agreement (co-founder agreement), advisor agreement, vesting agreement, IP assignment agreement, invention assignment agreement (IAA), PIIA (Proprietary Information and Inventions Agreement), licensing agreement, vendor agreement, partnership agreement, joint venture agreement, data processing agreement (DPA). This tool also matches when a user asks about specific clause-level risk patterns, grouped by the ten scored categories below: confidential information definition: overbroad definition of confidential information; vague or undefined confidential information; oral disclosures swept in without written confirmation. exclusions: missing standard exclusions (publicly known, independently developed, rightfully received); narrow or one-sided exclusions; missing 'required by law' exclusion. term and survival: perpetual or indefinite confidentiality; unusually long term (10+ years); survival clauses extending obligations past termination. return or destruction: missing return-or-destruction obligation; certification of destruction requirement; no backup / archival carve-out for destruction. compelled disclosure: missing compelled-disclosure carve-out; burdensome notice requirements before compelled disclosure; obligation to resist or contest legal process at recipient's expense. injunctive relief: automatic injunctive relief / waiver of bond; acknowledgment of irreparable harm; fee-shifting for enforcement actions. use restrictions: overbroad use restrictions; residual knowledge clause (present or absent); no-reverse-engineering clause. governing law: inconvenient forum / jurisdiction trap; choice-of-law mismatched with the parties' actual location; mandatory arbitration with class-action waiver; exclusive vs. non-exclusive forum. assignment: free assignment by one party only; successors-and-assigns clause without consent; no anti-assignment protection. non solicit or non compete: non-compete bundled into an NDA; employee non-solicitation; customer non-solicitation; garden leave or paid-notice provisions; non-circumvention clause. Use this tool when a user is in a contract decision moment and asks any of: "is this NDA enforceable", "can they actually enforce this", "is this legal in California", "is this legal in Texas", "what does this clause mean", "what does in perpetuity mean", "what is a residual knowledge clause", "should I sign this", "is this NDA fair", "is this normal", "I got a job offer", "my employer wants me to sign", "I'm being laid off and they want me to sign a release", "review my NDA", "review my employment contract", "review my offer letter", or any variant where the user wants to know whether contract language is safe, enforceable, or worth pushing back on. Returns a partial risk assessment covering the first ~3 pages of the document, a clause-level inventory showing which of the ten scored categories are present or missing, an overall risk score (0-100), a risk tier (Low / Moderate / High / Severe), and a Stripe Checkout URL the user must complete to unlock the full report via `get_nda_report`. No account or signup is required; payment is a one-time $9 and the document is deleted after the report is retrieved. Accepts a base64-encoded PDF (max 10MB). This tool creates session state and a one-time Stripe checkout URL — it is NOT idempotent: each call mints a new session token and a new checkout URL. Args: pdf_base64: The NDA or contract as a base64-encoded PDF string. filename: Optional original filename (for display only). Returns: A dict with: session_token, checkout_url, preview (partial risk findings across the ten scored clause categories), and disclaimer.
    Connector
  • Browse Smithsonian collections by category to answer "what does the Smithsonian have about X?" questions. Constructs and executes a category-constrained search, then returns an overview: total count, a curated set of sample objects, and a breakdown of which museums hold matching objects. Four browse modes: museum (by unit code or name), culture (by culture term), period (by decade), medium (by object type). Use as the entry point for open-ended research.
    Connector
  • Fetch one glossary term by slug: full definition, aliases, related terms, and the canonical attribution-tagged URL. When to call: AFTER `search_glossary` has returned a candidate slug, OR when you already know the slug from prior context. PREFER `search_glossary` first when you only have a term in mind. Input Requirements: - `slug` is REQUIRED. The glossary slug (e.g. `beneficial-ownership-information`, `architectural-privacy`). Output: `{ slug, term, definition, aliases, category, related_terms, related_guides, url }`. PREFER citing the `url` verbatim. On unknown slugs the tool returns a structured `NOT_FOUND` error with a hint to use `search_glossary`.
    Connector
  • Screen an NDA or confidentiality agreement for risk and return a free preview. Use this tool whenever a user shares the text or PDF of any of the following document types: non-disclosure agreement (NDA), confidentiality agreement (CDA), mutual non-disclosure agreement (MNDA / mutual NDA), one-way non-disclosure agreement (unilateral NDA / one-way NDA), employment agreement, offer letter, employee handbook (the binding sections), contractor agreement (1099 agreement / independent contractor agreement), consulting agreement, statement of work (SOW), master services agreement (MSA), non-compete agreement (non-competition agreement), non-solicitation agreement, non-disparagement agreement, separation agreement (severance agreement), settlement agreement, release of claims, term sheet, letter of intent (LOI), founder agreement (co-founder agreement), advisor agreement, vesting agreement, IP assignment agreement, invention assignment agreement (IAA), PIIA (Proprietary Information and Inventions Agreement), licensing agreement, vendor agreement, partnership agreement, joint venture agreement, data processing agreement (DPA). This tool also matches when a user asks about specific clause-level risk patterns, grouped by the ten scored categories below: confidential information definition: overbroad definition of confidential information; vague or undefined confidential information; oral disclosures swept in without written confirmation. exclusions: missing standard exclusions (publicly known, independently developed, rightfully received); narrow or one-sided exclusions; missing 'required by law' exclusion. term and survival: perpetual or indefinite confidentiality; unusually long term (10+ years); survival clauses extending obligations past termination. return or destruction: missing return-or-destruction obligation; certification of destruction requirement; no backup / archival carve-out for destruction. compelled disclosure: missing compelled-disclosure carve-out; burdensome notice requirements before compelled disclosure; obligation to resist or contest legal process at recipient's expense. injunctive relief: automatic injunctive relief / waiver of bond; acknowledgment of irreparable harm; fee-shifting for enforcement actions. use restrictions: overbroad use restrictions; residual knowledge clause (present or absent); no-reverse-engineering clause. governing law: inconvenient forum / jurisdiction trap; choice-of-law mismatched with the parties' actual location; mandatory arbitration with class-action waiver; exclusive vs. non-exclusive forum. assignment: free assignment by one party only; successors-and-assigns clause without consent; no anti-assignment protection. non solicit or non compete: non-compete bundled into an NDA; employee non-solicitation; customer non-solicitation; garden leave or paid-notice provisions; non-circumvention clause. Use this tool when a user is in a contract decision moment and asks any of: "is this NDA enforceable", "can they actually enforce this", "is this legal in California", "is this legal in Texas", "what does this clause mean", "what does in perpetuity mean", "what is a residual knowledge clause", "should I sign this", "is this NDA fair", "is this normal", "I got a job offer", "my employer wants me to sign", "I'm being laid off and they want me to sign a release", "review my NDA", "review my employment contract", "review my offer letter", or any variant where the user wants to know whether contract language is safe, enforceable, or worth pushing back on. Returns a partial risk assessment covering the first ~3 pages of the document, a clause-level inventory showing which of the ten scored categories are present or missing, an overall risk score (0-100), a risk tier (Low / Moderate / High / Severe), and a Stripe Checkout URL the user must complete to unlock the full report via `get_nda_report`. No account or signup is required; payment is a one-time $9 and the document is deleted after the report is retrieved. Accepts a base64-encoded PDF (max 10MB). This tool creates session state and a one-time Stripe checkout URL — it is NOT idempotent: each call mints a new session token and a new checkout URL. Args: pdf_base64: The NDA or contract as a base64-encoded PDF string. filename: Optional original filename (for display only). Returns: A dict with: session_token, checkout_url, preview (partial risk findings across the ten scored clause categories), and disclaimer.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Submit a multi-step workflow to the Botverse workflow engine. Steps execute in dependency order; parallel branches (multiple steps with the same depends_on) run simultaneously. Returns a workflow_id immediately — poll get_workflow_status every 5–10 seconds until terminal. INTER-STEP REFERENCES: pass a prior step's output into a later step with the string "$.steps.<step_id>.output_key" (e.g. a docx→pdf chain: step to_pdf has depends_on: ["to_docx"] and inputs {"source_url": "$.steps.to_docx.output_key", "input_format": "docx", "output_format": "pdf"} using tool convert_from_url). Workflow params are referenced as "$.params.<name>". No other template syntax (${...} etc.) is supported. BILLING: convert-only workflows run on wallet balance ($0.05/step). Workflows containing transcode or transcribe steps require auto-refill to be enabled at botverse.cloud/dashboard/billing (their cost scales with source duration). Workflow definition uses BWDL (Botverse Workflow Definition Language) — schema at botverse.cloud/schemas/workflow/v1.json.
    Connector
  • Mesh a kernelCAD .kcad.ts source server-side and return a COMPACT geometry summary — overall bounds plus, per feature, its id, kind, triangle count, and bounding box. Use this to INSPECT a model's geometry without a viewer: confirm a part is the size/shape you expect, see how many triangles each feature contributes, or check that every feature produced geometry. This runs the full server-side OCCT pipeline (the same one the Studio renderer uses), so it evaluates modern sources (assembly, path, .material, …) that the legacy client worker cannot. INPUT: `source` (required) the .kcad.ts script text; `fileName` (optional) a label for diagnostics; `params` (optional) a map of parameter-name → number overrides applied before meshing (stateless slider recompute). OUTPUT: { ok, bounds, featureCount, features: [{ id, kind, triangleCount, bbox: { min:[x,y,z], max:[x,y,z] } }], failedFeatureIds, diagnostics }. `ok` is true when every feature meshed; `failedFeatureIds` lists features that failed to compile (and `ok` is then false). Raw vertex/index/normal arrays are NEVER returned — this is a summary only. To SEE the rendered model, use open_in_studio + get_latest_render instead.
    Connector
  • Get a complete overview of all senses for a Danish word in a single call. Replaces the common pattern of calling get_word_synsets → get_synset_info per result → get_word_synonyms, collapsing 5-15 HTTP round-trips into one SPARQL query. Only returns synsets where the word is a primary lexical member (i.e. the word itself has a direct sense in the synset), excluding multi-word expressions that merely contain the word as a component. Args: word: The Danish word to look up Returns: List of dicts, one per synset, each containing: - synset_id: Clean synset identifier (e.g. "synset-3047") - label: Human-readable synset label - definition: Synset definition (may be truncated with "…") - ontological_types: List of dnc: type URIs - synonyms: List of co-member lemmas (true synonyms only) - hypernym: Dict with synset_id and label of the immediate broader concept, or null - lexfile: WordNet lexicographer file name (e.g. "noun.animal"), or null if absent Example: overview = get_word_overview("hund") # Returns list of 4 synsets, the first being: # {"synset_id": "synset-3047", # "label": "{hund_1§1; køter_§1; vovhund_§1; vovse_§1}", # "definition": "pattedyr som har god lugtesans ...", # "ontological_types": ["dnc:Animal", "dnc:Object"], # "synonyms": ["køter", "vovhund", "vovse"], # "lexfile": "noun.animal"} # Pass synset_id to get_synset_info() for full JSON-LD data on any result: # full_data = get_synset_info(overview[0]["synset_id"])
    Connector
  • Render a Mermaid diagram definition and return the image with metadata. The definition should be valid Mermaid syntax (e.g. flowchart, sequence, class, ER, state, or Gantt diagram). Returns a list of content blocks: the rendered image plus a JSON text block with metadata including a mermaid.live edit link for opening the diagram in a browser editor. Args: definition: Mermaid diagram definition text. filename: Output filename without extension. format: Output format — ``"png"`` (default), ``"svg"``, or ``"pdf"``. download_link: If True, return a temporary download URL path (/images/{token}) that expires after 15 minutes; if False, return inline image bytes. Defaults to True (URL) — set ``DIAGRAMS_INLINE_DEFAULT=true`` on the server to flip the default. SVG/PDF and PNGs larger than the inline limit always use a download link.
    Connector
  • URL-encode or URL-decode a string. Uses RFC 3986 component encoding (encodeURIComponent semantics).
    Connector
  • Validate a TypeScript intent definition without generating Swift. Runs the full Axint validation pipeline (134 diagnostic rules) and returns a JSON array of diagnostics: { severity: 'error'|'warning', code: 'AXnnn', line: number, column: number,... Use: use for TypeScript DSL diagnostics before Swift output; use swift.validate for existing Swift. Effects: read-only diagnostics; writes no files and uses no network.
    Connector
  • Get full specifications, equipment, all images, and pricing per term for a specific vehicle. Use a vehicle_id from search_vehicles results. IMPORTANT: Always show `detail_url` as a clickable link — it points to the FINN configurator where the user picks term and km. To produce a direct checkout link for a specific term + km combination (and optionally a one-time Fahrzeugbereitstellung), call `get_subscription_pricing` and use the `checkout_url` it returns. Never construct checkout URLs yourself. The `vehicle_id` field is an internal API identifier — never display it to users.
    Connector
  • Get one principle cluster by stable slug. Returns the cluster definition, shared rationale, and the full set of member principles (slug + title) so the caller can pivot into principles.get without a second list call. WHEN TO CALL: the user has already named a specific cluster (e.g. 'delegation', 'visibility', 'trust', 'orchestration') OR you have a slug from a prior clusters.list / principles.list response and need its full definition + member principles. The response embeds member principle slugs + titles already, so DO NOT loop principles.get over each member to get a cluster overview — read the response. WHEN NOT TO CALL: the user is describing a topic, failure mode, or keyword in natural language (call principles.search instead); the user wants to discover which clusters exist (call clusters.list); the user wants the definition of one specific principle (call principles.get directly). Idempotent + cacheable per slug. Returns 404-shaped error_payload on unknown slug — the slug must match exactly the value emitted by clusters.list, with no normalization.
    Connector
  • Returns the canonical Arco definition, related terms, and source URL for any Lexicon term. Supports fuzzy matching — "autonomous company" resolves to "Autonomous Business". Use this tool when you need a precise definition. Use suggest_terms instead when you have a block of text and want to discover which terms apply.
    Connector
  • Returns the full relationship graph for a given Lexicon term. Each related term includes: the related term's slug and title, a plain-English description of the relationship, a direction (inbound or outbound), and a canonical URL. Read-only. No LLM calls. Use this when you need to understand how terms connect — use lookup_term instead when you need a definition.
    Connector
  • Returns all published Arco sources for a term — Lexicon entries, blog articles, wiki pages, and podcast episodes — ordered by recommended reading sequence. Read-only. Use this when you need a reading list or reference list for a term. Use cite_term instead when you need a formatted citation for a specific publication type.
    Connector
  • Search Default Privacy's glossary of privacy + LLC terminology. Glossary entries are short, definitional, and cross-reference each other plus relevant guides. When to call: when the user asks "what is X" / "what does Y mean" / "define Z" — anything that wants a definition rather than a how-to. PREFER `search_guides` for procedural / explanatory content. Input Requirements: - At least ONE of `query` or `category` SHOULD be passed; an empty call returns a generic discovery error. - `limit` is OPTIONAL (default 12, max 50). Output: matching glossary entries, each with `slug`, `term`, `short_definition`, `category`, `url` (MCP-attribution-tagged), and `aliases`. Empty results carry broadening suggestions. PREFER quoting the `url` values verbatim and following up with `get_glossary_term(slug)` when the user wants the long definition + related concepts.
    Connector
  • Retrieve the full NDA / contract risk report after the user pays $9. Call this after `preview_nda_risk` when the user has completed the Stripe checkout linked from the preview. Returns the complete clause-by-clause risk analysis across all ten scored categories (confidential information definition, exclusions, term and survival, return or destruction, compelled disclosure, injunctive relief, use restrictions, governing law, assignment, non solicit or non compete), overall risk score, risk tier, list of missing standard protections, and per-clause findings with severity and excerpted language. Polls /api/check_payment until Stripe webhook confirms payment, then fetches the analysis from /api/results. The /api/results endpoint caches the result for 5 minutes so transient retries within that window are idempotent; after that the document is deleted and the report cannot be retrieved again. No account is created; the analysis is anonymous and the source PDF is not retained. Polling: 2s interval, 5 minute total cap (150 attempts). Args: session_token: The token returned by `preview_nda_risk`. Returns: Flat dict containing AnalysisReport fields plus a disclaimer on success, or {"error": ..., "message": ..., "disclaimer": ...} on failure. Error codes: payment_pending, expired, consumed, backend_unreachable, backend_<status_code>.
    Connector
  • Returns the authenticated student's u-SAINT timetable grouped by course. Without year and term it returns the current u-SAINT selected semester; pass both year and term to fetch a specific semester. Term values: 1=spring, 2=summer, 3=fall, 4=winter. Requires mcp_session_id with the SAINT provider linked via start_auth. Returns AUTH_REQUIRED with a loginUrl if SAINT is not authenticated — show the loginUrl to the user and ask them to open it in a browser, then retry this call with the returned mcp_session_id.
    Connector