Skip to main content
Glama
753,393 tools. Updated 2026-11-06 21:06

"A guide to creating voiceovers" matching MCP tools:

  • Enumerate and inspect the validated operations scene_apply accepts — call this BEFORE reaching for scene_script. The DSL is large (mesh editing, booleans, lathe/loft/sweep, curves, UV unwrap, modifiers, materials, lights, cameras, render settings, geometry nodes, batch and query ops), so most modelling does NOT need raw bpy. No args: every namespace with counts. guide=true (or op="guide" for older connector catalogs): full operating guide. namespace="mesh": that namespace's operations. Repeated details are object.radial_array or object.array_along_curve (no "pattern" namespace). Use world.update for the environment; validation is the separate scene_validate tool. search="boolean": ranked matches. op="mesh.bevel": the full JSON Schema with types, ranges and defaults. Schemas are introspected from the validator itself, so they are always exactly what scene_apply will accept. Full schemas are returned once in structuredContent; format="text" returns them in text instead. This tool is READ ONLY and free — it queues no job, spends no compute and changes nothing — so it is always safe to retry, including after a transport-level error.
    ConnectorAPI key
  • 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
  • List the curated sandbox topic labels that define the free Discovery corpus — every topic federally-sourced and audience-safety-checked. Use it to preview what content domains exist before creating a stream. Does NOT enumerate messages — the corpus stays internal. For the full live template catalog + gating contract, read the signal://catalog resource.
    ConnectorNo auth
  • How to operate as a product manager on AIOProductOS. No arguments and no side effects — returns the same operating guide as plain text every call (deterministic): how to ground in the product brain, keep work welded to the spine (insight→feature→task→outcome), prioritise on evidence (affected accounts + MRR + reach), and what 'done' means. Call it FIRST, before planning or prioritising, to load the house rules the other tools assume.
    ConnectorNo auth
  • List the curated sandbox topic labels that define the free Discovery corpus — every topic federally-sourced and audience-safety-checked. Use it to preview what content domains exist before creating a stream. Does NOT enumerate messages — the corpus stays internal. For the full live template catalog + gating contract, read the signal://catalog resource.
    ConnectorNo auth
  • 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

Matching MCP Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    面向 Codex、WorkBuddy 等 AI 工具的知你AI助手合并版 Skills,涵盖当前会话分诊、客户查询与画像、历史会话检索、客户分群和 API Key 用量查询,并连接个微、企微、视频号、微信小程序、公众号、服务号、微信客服、微信小店、抖音号、小红书、微博、网站及H5客服等渠道。
    MIT No Attribution
  • A
    license
    Not graded
    quality
    C
    maintenance
    这是面向智能运维场景的 MCP 工具服务,让 Agent 能够按需检索日志内容并获取主机与应用的监控指标数据。它把实时的日志与指标证据接入 Plan-Execute-Replan 诊断流程,从而支撑自动故障排查与根因分析。
    3
    MIT

Matching MCP Connectors

  • 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
  • Display a holiday photo to the user by creating an HTML artifact that embeds the photo from its hosted URL. After calling this tool you MUST create an HTML artifact (type text/html) whose body is a single <img> tag pointing at the hosted URL returned in the result. Do not write a prose description, caption, or commentary — the user wants to view the photo, not read about it. Use list_photos first to discover valid IDs.
    ConnectorNo auth
  • Creates a WhatsApp group and adds the given participants. This NOTIFIES everyone you add and cannot be undone if the participant list is wrong, so it is a write operation: the first call (confirm=false) returns a preview of the name + participants without creating anything; set confirm=true to actually create. Resolve numbers first with whatsapp_search_contacts.
    Connector
    Destructive
    OAuth
  • Read remaining quotas and plan entitlement for the authenticated company. Call this when you need to know whether an active plan is in effect before registering OIDC clients or creating login links. Creating login links, minting extra API keys, and registering end users all require an active plan (the bootstrap key does not). Requires a company API key (aa_...) or an MCP OAuth access token. Returns planId, planStatus, periodYm, included, used, remaining, and hardCap. It does not change billing or charge a card. To start a human Pro checkout, use billing_checkout. billing_machine_pay only returns prepaid REST instructions. To manage an existing Stripe subscription, use billing_portal.
    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
  • Add one vote to an existing feature request — the 'me too' signal for something already filed, instead of creating a duplicate. Call once per distinct person/session you're voting on behalf of; there is currently no per-voter dedupe, so an agent must not call this repeatedly for the same requester to inflate the count.
    ConnectorAPI key
  • Scaffold a flags-only Bridge integration into an existing project — the MCP equivalent of `bridge flag init`. Returns everything that command produces, for YOU to write to disk: the contents of bridge-flags.config.json (app id, app name, base URL, suggested provider config, read live from this Bridge app), the install command, and the framework-specific setup guide fetched from the plugin repo that owns it. Writes nothing — neither to disk nor to the Bridge app. Call this when adding feature flags to a project for the first time; for auth or billing use get_integration_guide with topic=master or topic=billing-master instead. framework is REQUIRED: this server cannot see the caller's disk, so detect it yourself from package.json (next → nextjs, @sveltejs/kit or svelte → svelte, @nestjs/core → nestjs, @angular/core → angular, react → react, express → express; check in that order) and pass it. The returned guide is the same document get_integration_guide returns for topic=feature-flags, so there is no need to call both. Do not invent import specifiers — they differ per plugin and only the guide has the current ones.
    ConnectorOAuth
  • The real emergency number and crisis lines for a country. Use FIRST, before any other tool, when someone speaks of harming themselves or others or is in danger. Never defaults to a country: ask if unknown. Example: {country:"Kenya"}. Full guide: living-bread://tools/get_crisis_help. Access: no sign-in; shared limit of 300 requests a minute per IP.
    ConnectorNo auth
  • Create a new, empty signature folder to organize signature templates. Folders created here are top-level (not nested). Use it only when no suitable folder exists: call list_folders first to reuse one, and use update_folder to rename an existing folder instead of creating another, since duplicate names are allowed. Creating a folder files nothing: to put a signature in it, pass the returned `id` as `folder_id` to create_signature or update_signature. Writes one folder and returns it with `signature_count` 0. Needs the folders:write scope; a blank name returns 422.
    ConnectorOAuth
  • Creates a new folder inside a workspace, optionally nested under a parent folder. Folder names must be unique among siblings (case-sensitive, max 80 chars) and nesting is capped at 5 levels. Returns the created folder row. Use list_folders first to look up the parent_id when creating a subfolder.
    ConnectorOAuth
  • Get the current value of a figure a reference quotes with a date. Use this when a reference quotes a figure from an OptimToken guide ("measured on the 2026-10-25 OptimToken catalogue") and the answer needs the current value: the Compute Savings Plan or reservation discount, the gap between a flexible and a locked commitment, the ARM discount against Intel and AMD, the share of LLM models with a batch rate. It fetches the guide's figures file, rebuilt daily, and returns it as published. Args: guide: The guide slug, lowercase letters, digits and hyphens. Guides with figures today: ``"savings-plans-vs-reserved-instances"``, ``"arm-against-x86"``, ``"batch-api-economics"``. Returns ``{"document": {...}, "fetched_at": ..., "source": "live" | "cached", "note": ...}``, plus ``cache_age_seconds`` when cached (six-hour cache). ``document`` is the file unchanged: ``guide``, ``title``, ``url``, ``dataSource``, ``snapshotDate`` (the catalogue the figures come from), ``dateModified`` and ``figures``, where discounts are fractions (0.2743 is 27.4%) and each key names a median, a range or a count. An unknown slug returns ``{"error", "available_guides", "suggestions"}``. Any other failure (timeout, HTTP error, invalid JSON) returns ``{"error", "fallback"}``: the dated figure in the reference then stands, quoted with its date.
    ConnectorNo auth
  • Create a new list for the user (e.g. 'make a Costco list', 'start a party list', 'set up a baby registry'). Defaults to a shopping list. The list appears in the user's LastList app and is labeled as created by you. Ask the user before creating a list they didn't request.
    ConnectorOAuth
  • Read remaining quotas and plan entitlement for the authenticated company. Call this when you need to know whether an active plan is in effect before registering OIDC clients or creating login links. Creating login links, minting extra API keys, and registering end users all require an active plan (the bootstrap key does not). Requires a company API key (aa_...) or an MCP OAuth access token. Returns planId, planStatus, periodYm, included, used, remaining, and hardCap. It does not change billing or charge a card. To start a human Pro checkout, use billing_checkout. billing_machine_pay only returns prepaid REST instructions. To manage an existing Stripe subscription, use billing_portal.
    ConnectorAPI key
  • Create a local container snapshot (async). Runs in background — returns immediately with status "creating". Poll list_snapshots() to check when status becomes "completed" or "failed". Available for VPS, dedicated, and cloud plans (any plan with max_snapshots > 0). Local snapshots are stored on the host disk and count against disk quota. Requires: API key with write scope. Args: slug: Site identifier description: Optional description (max 200 chars) Returns: {"id": "uuid", "name": "snap-...", "status": "creating", "storage_type": "local", "message": "Snapshot started. Poll list_snapshots() to check status."} Errors: VALIDATION_ERROR: Max snapshots reached or insufficient disk quota
    ConnectorNo auth