"Slides" matching MCP tools:

• query_power_interconnection_queue_ercot_v1

  osint

  Query the ERCOT generator interconnection queue — ERCOT's public GIS Report (EMIL PG7-200-ER), the waiting line of generation projects that have REQUESTED to connect to the ERCOT (Texas) grid. Returns cited, project-level records with ERCOT's full published structure across four lifecycle sheets (Large Gen + Small Gen = active; Inactive Projects; Cancellation Update): the requested `capacity_mw` (ERCOT publishes ONE capacity figure — no summer/winter split), the ERCOT `fuel` and `technology` codes (e.g. SOL/PV solar, OTH/BA battery, GAS/CC combined-cycle, WIN/WT wind — HYD is HYDROGEN, hydro is WAT), the `cdr_reporting_zone` (NORTH/SOUTH/WEST/COASTAL/HOUSTON/PANHANDLE), the `interconnecting_entity`, the `poi_location`, the composite `gim_study_phase` token string, and the milestone dates (`screening_study_started`, `fis_approved`, `ia_signed`, `construction_start`/`construction_end`, `approved_for_energization`/`approved_for_synchronization`, `projected_cod`). Group or filter by `application_status`, `size_category`, `fuel`, `technology`, `cdr_reporting_zone`, `county_fips`, `state`, `gim_study_phase`, or `interconnecting_entity`; filter `projected_cod` by the `projected_cod_from` / `projected_cod_to` range. Pass each parameter as a top-level key of `params` (flat — not nested). Example: `{"application_status": "ACTIVE", "fuel": "SOL"}` for active solar requests; `{"application_status": "ACTIVE", "group_by": ["fuel"], "order_by": "capacity_mw", "top_n": 5}` for the active pipeline's biggest fuels by requested MW. The GIS Report is published MONTHLY and its full history is queryable — this is NOT a single point-in-time snapshot. Omit `as_of` for the latest month, or pass `as_of` (a date) to get the queue as it stood at a past month: `as_of` resolves to the newest monthly snapshot at or before it, with vintages back to 2018-12 (the floor; an earlier `as_of` is refused, naming the floor). Example: `{"application_status": "ACTIVE", "as_of": "2019-06-30"}` returns the active queue as of mid-2019. Each month is a full point-in-time snapshot (a project that has since withdrawn is simply absent from later months — query the earlier `as_of` to see it), so a multi-month trend is one query per month; `as_of` is the history axis, not a row filter. Returns JSON aggregates with citations and optional row-level records when `include_records` is true; every value carries `source`, `as_of`, and a `source_row` verifiable with get_source_evidence_v1. `capacity_mw` is REQUESTED capacity, not built: historically the large majority of queued megawatts withdraw before they are built. NEVER read a queue-MW total as installed or operating capacity — it is additive across distinct rows but is a REQUESTED total only. ERCOT prints NO status column, so `application_status` is derived from the sheet ERCOT files the project on: `ACTIVE` is the live pipeline (Large/Small Gen), `INACTIVE` and `CANCELLED` are projects that recently left the queue (the Inactive / Cancellation sheets list RECENT departures, NOT the full historical withdrawn set). The build-progress reading is carried SEPARATELY in `gim_study_phase` (e.g. "SS Completed, FIS Completed, IA") + the milestone dates and is never collapsed into `application_status`. For built/operating capacity use query_power_capacity_v1. ERCOT only — never summed, deduped, or compared across ISOs. For the MISO interconnection queue use query_power_interconnection_queue_v1; for PJM use query_power_interconnection_queue_pjm_v1 (or query_power_interconnection_queue_pjm_cycle_v1 for PJM's cluster/cycle grid); for the CAISO (California) queue use query_power_interconnection_queue_caiso_v1; for the NYISO (New York) queue use query_power_interconnection_queue_nyiso_v1; for the ISO-NE (New England) queue use query_power_interconnection_queue_isone_v1; for the SPP (central US) queue use query_power_interconnection_queue_spp_v1. This tool serves ERCOT's GIS Report, which is GENERATION-only; ERCOT's separate large-load / data-center interconnection queue is an unstructured source (TAC-meeting PDF slides) and is NOT served here, and this tool does not infer which projects are data-center-driven — that interpretation is the analyst's, from cited rows.

  Connector

• check_prompt

  Nullcone Threat Intelligence

  Check a prompt or text fragment for known PROMPT IOC patterns. Uses an in-memory hash set for sub-1ms token-level querying — no network calls after the cache is warmed. Slides a window of 3, 5, 8, and 10 tokens across the input and checks each window's canonical SHA256 against the PROMPT IOC feed. This is the primary real-time prompt injection detection endpoint. Call it on every user-supplied prompt before passing to the LLM. Args: text: The prompt text to check (raw, any length) auto_warm: If True and cache is empty, warm it first (adds ~300ms on first call only). Default True. Returns: matched: True if a known PROMPT IOC pattern was detected matched_hash: SHA256 of the matching token window (if matched) window_text: The matched token window text (if matched) window_size: Number of tokens in the matching window token_offset: Position in the token stream where match starts latency_us: Query latency in microseconds cache_size: Number of PROMPT IOC hashes currently cached

  Connector

• create_page

  tela

  Create a page in a space (editor+). Body is markdown; tela://page/{id} links and [[Page Title]] wikilinks (resolved by title within the space) are indexed as backlinks. tela renders a rich block palette beyond plain markdown — to-do list, pull quote, callout, collapsible, tabs, kanban board, stat grid, timeline, calendar, poll, chart, embed, mermaid diagram, image, file attachment, code block, equation, inline math, table, highlight, wikilink, footnote. Prefer these over walls of text; read the tela://authoring-guide resource (or this server's instructions) for exact syntax. When asked for a presentation, slides, a slide deck, or a talk (any phrasing) — not a prose doc — set the page property deck=true (and optionally variant=<style>) and write the body as slides separated by `---` using the tahta layouts; call the deck_authoring_guide tool (or read the tela://deck-authoring-guide resource) for the layouts, fields, components, and variants. When asked for a spreadsheet, a table of data with formulas/totals, a budget, a tracker, or any grid that computes — not a prose doc — set the page property sheet=true and write the body as Defter markdown (compact GFM tables + an optional ```defter-style block); call the sheet_authoring_guide tool (or read the tela://sheet-authoring-guide resource) for the format, formulas, and styling.

  Connector

• list_themes

  Slidev MCP

  Get a list of all available themes with style descriptions and recommendations. Call this to decide which theme to use. Returns a guide organized by style (dark, academic, modern, playful, etc.) with "best for" recommendations. After picking a theme, call get_theme with the theme name to read its full documentation (layouts, components, examples) before rendering. This tool does NOT display anything to the user — it is for your own reference when choosing a theme.

  Connector

• weekly_project_update_ppt

  L&T MCP

  SKILL: weekly_project_update_ppt Team: Project Management Weekly Project Update PPT — L&T Format Call this tool to get the complete guide for 'weekly_project_update_ppt'. Read the 'content' field and follow its instructions. This tool takes NO parameters. Full content: --- name: weekly_project_update_ppt description: > Use this skill to create a weekly project update PowerPoint presentation in L&T branded format. Use when user asks for weekly update, weekly report, project status PPT or weekly project summary presentation. --- # Weekly Project Update PPT — L&T Format ## When To Use - "Create weekly update for project X" - "Make weekly PPT for project LE20M143" - "Generate project status presentation for this week" - "Weekly report PPT" --- ## Step 1 — Collect Information From User Ask the user for all of these in ONE message before doing anything. NEVER assume or fill in values yourself. Ask exactly this: ``` To create your weekly project update PPT I need the following: 1. 📋 Project Name (e.g. Mumbai Metro Line 7) 2. 📌 Project Code (e.g. LE20M143) 3. 📅 Week Number (e.g. Week 24) 4. 📅 Date Range (e.g. 09-Jun-2025 to 15-Jun-2025) 5. ✅ Accomplishments This Week (list what was completed) 6. 📌 Planned Next Week (list what is planned) 7. ⚠️ Risks & Issues (list risks, mention HIGH / MEDIUM / LOW if known) 8. 👤 Prepared By (your name) ``` Wait for the user to reply with all details. Do NOT move to Step 2 until user has provided the information. --- ## Step 2 — Generate The PPT Use the execute_code tool to generate a 5 slide PowerPoint file. Use python-pptx library. Download the L&T logo from this URL and place it on every slide: https://upload.wikimedia.org/wikipedia/commons/thumb/c/cd/L%26T.png/320px-L%26T.png If the logo cannot be downloaded, write the text "L&T" in orange as a substitute in the same position. --- ## Slide Specifications ### SLIDE 1 — Title Slide Background: Full navy blue (#002B5C) covering the entire slide Top of slide: - Thin orange (#F47B20) horizontal bar across the full width at the very top - L&T logo placed top right corner - Text "L&T Construction" in small orange text top left Center of slide: - Large white bold text: "Weekly Project Update" - Below that in orange bold text: the Project Name - Small navy chip/box containing the Project Code in orange text - Below that in white normal text: Week Number and Date Range - Below that in grey text: "Prepared by: [name]" Bottom of slide: - Thin orange horizontal bar across the full width at the very bottom - Small grey italic text: "Generated by L&T Enterprise MCP Agent" with today's date and time --- ### SLIDE 2 — Accomplishments This Week Background: Light grey (#F4F4F4) covering the entire slide Header bar at top: - Full width navy blue bar, height about 1 inch - White bold text on the left: "✅ Accomplishments This Week" - Below the title in small orange text: Week Number and Date Range - L&T logo on the right side of the header bar - Thin orange line immediately below the navy header bar Content area: - White rounded rectangle card covering most of the slide - Thin orange vertical stripe on the left edge of the card - Each accomplishment as a bullet point using a right arrow symbol - Font size 16, dark grey color - Adequate spacing between bullets so it is easy to read Footer bar at bottom: - Full width navy blue bar - White small text on left: "L&T Construction | Confidential | For Internal Use Only" - Orange small text on right: "Prepared by: [name]" --- ### SLIDE 3 — Plan for Next Week Background: Light grey (#F4F4F4) covering the entire slide Header bar at top: - Same style as Slide 2 - Title text: "📌 Plan for Next Week" - L&T logo on the right side of the header bar Content area: - White rounded rectangle card covering most of the slide - Thin navy blue vertical stripe on the left edge of the card (navy stripe instead of orange to visually distinguish from Slide 2) - Each planned item as a bullet point using a right arrow symbol - Font size 16, dark grey color - Adequate spacing between bullets Footer bar: - Same style as Slide 2 --- ### SLIDE 4 — Risks & Issues Background: Light grey (#F4F4F4) covering the entire slide Header bar at top: - Same style as Slide 2 - Title text: "⚠️ Risks & Issues" - L&T logo on the right side of the header bar Content area — Table: - Table with two columns: "Risk / Issue" and "Severity" - Table header row: navy blue background with white bold text - Data rows alternate between white and light grey background - "Risk / Issue" column takes about 75% of the width - "Severity" column takes about 25% of the width - Each severity value shown as a colored pill/badge: HIGH → red (#DC3545) pill with white text MEDIUM → amber/orange (#FFA500) pill with white text LOW → green (#28A745) pill with white text - If user did not specify severity, default to MEDIUM - Show maximum 6 risks in the table - Below the table show a small legend: 🔴 HIGH — Immediate action required 🟡 MEDIUM — Monitor closely 🟢 LOW — Awareness only Footer bar: - Same style as Slide 2 --- ### SLIDE 5 — Closing Slide Background: Full navy blue (#002B5C) covering the entire slide Same orange bars at top and bottom as Slide 1 Center of slide: - L&T logo centered in the upper half - Large white bold text below logo: "Thank You" - Orange text below: Project Name and Project Code - White text below: Week Number and Date Range Bottom area: - Small grey italic text centered: "L&T Construction — Enterprise Information Platform" --- ## Overall Design Rules Colors: - Primary background (dark slides): Navy blue #002B5C - Primary background (content slides): Light grey #F4F4F4 - Cards and content boxes: White #FFFFFF - Accent color: Orange #F47B20 - Body text: Dark grey #444444 - Footer text: White on navy backgrounds - Headings on dark backgrounds: White - Headings on light backgrounds: Navy blue Typography: - Main title on title slide: 38pt bold white - Slide titles in header bar: 22pt bold white - Project name on title slide: 26pt bold orange - Bullet points: 16pt dark grey - Footer text: 8pt - Week/date labels: 9-10pt orange Logo placement: - Title slide: top right, width about 1.9 inches - Content slides: right side of the navy header bar, width about 1.3 inches - Closing slide: centered, width about 2.1 inches Slide size: 13.33 inches wide by 7.5 inches tall (widescreen 16:9) Every content slide must have: - Navy header bar at top with title and logo - Thin orange line below the header bar - Navy footer bar at bottom with confidentiality note and prepared by --- ## Step 3 — Save and Return Save the file with this name format: Weekly_Update_{ProjectCode}_{WeekNumber without spaces}.pptx Example: Weekly_Update_LE20M143_Week24.pptx After the file is generated show this to the user: ``` ✅ Your Weekly Project Update PPT is ready! 📎 Download: {download_url} 📋 Project: {Project Name} ({Project Code}) 📅 Period: {Week Number} | {Date Range} 📊 Slides: 5 slides generated 1. Title 2. Accomplishments This Week 3. Plan for Next Week 4. Risks & Issues 5. Closing File expires in 24 hours — please download promptly. ``` --- ## Important Rules - NEVER generate the PPT without collecting user input first - NEVER make up project name, code, dates or any content - ALWAYS download the L&T logo from the URL given above - ALWAYS use navy and orange as the primary colors - ALWAYS include the logo on every slide - ALWAYS include the footer on every content slide - ALWAYS call execute_code tool — never just describe the slides - ALWAYS show the download link to the user after generation - If execute_code returns an error, fix the code and retry up to 3 times

  Connector

• generate_deck_image

  tela

  Generate an image from a prompt and attach it to a deck page (editor+), ready for a bg:/image: slot. Returns the serve URL + a  snippet; reference it by path (don't regenerate on re-render). Read the imagery module first (deck_authoring_guide module="imagery"): most slides need NO image — use it for atmosphere/concept/focal only, reuse ONE background, write rich on-palette prompts, and prefer images raw. May be unavailable (503) if the instance hasn't configured image generation or AI is paused; generation can take from ~20s to a few minutes depending on the model.

  Connector

• render_slides

  Slidev MCP

  Render a Slidev presentation from markdown and return its hosted URL. IMPORTANT: Before calling this tool, you MUST call get_theme with the theme name you plan to use. Each theme has unique layouts, components, and frontmatter options. Apply the theme's specific features in your markdown to produce high-quality slides that match the theme's design. If the user has not specified a theme, call list_themes to pick one. If you are unfamiliar with Slidev markdown syntax, call get_slidev_guide. Images must be remote URLs or base64-encoded inline. Local file paths are not supported.

  Connector

• browse_themes

  Slidev MCP

  Show the user a visual theme gallery with preview images. ONLY call this when the user explicitly asks to SEE or BROWSE themes visually (e.g. "show me the themes", "what do they look like", "let me pick a theme"). This renders an interactive gallery in the user's UI. To show a filtered subset (e.g. only dark themes), first call list_themes to identify matching themes, then pass their names here. Do NOT call this to decide which theme to use yourself — use list_themes for that instead.

  Connector

• webdiet_list_anexos

  WebDiet

  Load educational slides or cloud file attachments. Use laminasAnexos for educational slides/laminas (~238 items with PDFs about nutrition topics), cloudAnexos for uploaded cloud files. For guidelines/orientations specifically, use webdiet_orientacoes action=list_banco. Bulk support: accepts patient_ids for batched execution.

  Connector

• update_page

  tela

  Patch a page's title and/or body (editor+). A body change auto-snapshots a revision. tela renders a rich block palette beyond plain markdown — to-do list, pull quote, callout, collapsible, tabs, kanban board, stat grid, timeline, calendar, poll, chart, embed, mermaid diagram, image, file attachment, code block, equation, inline math, table, highlight, wikilink, footnote. Prefer these over walls of text; read the tela://authoring-guide resource (or this server's instructions) for exact syntax. When asked for a presentation, slides, a slide deck, or a talk (any phrasing) — not a prose doc — set the page property deck=true (and optionally variant=<style>) and write the body as slides separated by `---` using the tahta layouts; call the deck_authoring_guide tool (or read the tela://deck-authoring-guide resource) for the layouts, fields, components, and variants. When asked for a spreadsheet, a table of data with formulas/totals, a budget, a tracker, or any grid that computes — not a prose doc — set the page property sheet=true and write the body as Defter markdown (compact GFM tables + an optional ```defter-style block); call the sheet_authoring_guide tool (or read the tela://sheet-authoring-guide resource) for the format, formulas, and styling.

  Connector

• list_session_slides

  Slidev MCP

  List all slide presentations created in the current MCP session. Returns URLs, themes, and timestamps for each presentation you've created.

  Connector

• get_theme

  Slidev MCP

  Get full documentation for a specific theme: layouts, components, and examples. Call this BEFORE render_slides to learn the theme's unique features. Each theme has different layouts, components, and frontmatter options. Use what you learn here to produce high-quality, theme-specific slides. This is the primary tool for preparing to render slides. When the user specifies a theme, call this directly — no need to call browse_themes.

  Connector

• get_slidev_guide

  Slidev MCP

  Get the Slidev syntax guide: how to write slides in markdown. Returns the official Slidev syntax reference (frontmatter, slide separators, speaker notes, layouts, code blocks) plus built-in layout documentation and an example deck. Call this once to learn how to write Slidev presentations.

  Connector

• niche_draft_revise

  Niche — Editorial Intelligence

  Applies the values you pass to a specific output. Accepts any subset of the output's fields: caption, hashtags, or partial script updates (hook / body / cta / hook_tweet / body_tweets / title / subtitle / pull_quote / cover_slide / slides / cta_slide / alt_text / card_headline, where card_headline rewords the image card's header). Pass `apply_hook_variant_index` to splice an existing hook_variants[N] into the live hook in one move without rewriting the rest. If you pass no editable field (or values identical to the current draft) it changes nothing and returns `status:'no_change'` naming the params that edit content. Angle and story changes still go back through niche_angle_propose; they invalidate the verifier trust block and need fresh generation. Response includes a `diff[]` array listing every field that changed (`{field, before, after}`) so agents can show users the delta rather than the full new payload.

  Connector

• gdrive_read_file

  local-mcp

  Reads a text file from the synced Google Drive folder (.txt, .md, .csv, .json, code files...). Note: native Google Docs/Sheets/Slides sync as .gdoc/.gsheet pointers, not real files — export them from Drive or read Office/PDF copies instead. Auto-detects UTF-8 with Latin-1/CP1252 fallback.

  Connector

• lint_deck

  tela

  Validate a deck page's slides against the tahta theme contract — unknown layouts, missing required fields, type/format mistakes. Run after authoring/editing a deck to catch problems before presenting. Returns structured issues per slide. For the full list of valid layouts and each layout's fields, call deck_authoring_guide.

  Connector

• generate_presentation

  Alai

  Generate a presentation from text content. Returns a generation_id to poll. Args: input_text: Content to transform into slides (text, markdown, or notes) title: Presentation title theme_id: Theme ID to use for the presentation. Call get_themes to discover available theme IDs and names for the authenticated user. vibe_id: Vibe ID for visual style. Call get_vibes to discover available vibes. Requires num_creative_variants >= 1 when set. slide_range: Target slides - 'auto', '1', '2-5', '6-10', '11-15', '16-20', '21-25', '26-50', '51-100' additional_instructions: Extra guidance for the AI include_ai_images: Whether to generate AI images for slides num_creative_variants: Number of creative slide variants (0-2). Increases cost. image_ids: IDs of previously uploaded images to incorporate into slides. total_variants_per_slide: Number of distinct slide options to generate (1-4). export_formats: Output formats - 'link', 'pdf', 'ppt'. Defaults to ['link']. language: Output language, e.g. "French", "Japanese", "Spanish (Latin America)". If not set, matches the input language. Poll get_generation_status until status is 'completed'.

  Connector

• pitch_deck_storyline

  gapup-mcp

  Build a complete investor pitch-deck storyline for a company. Returns an 8-20 slide narrative tailored to the target audience (seed-vc / series-a-vc / growth-vc / strategic / bank / grant) — each slide carrying a title, key points, a speaker note and a visual hint — plus a Q&A bank of 10-15 likely board questions and traps to avoid. Output is deck JSON ready to export to Google Slides, Notion or Pitch.com. When to use this tool: the user is preparing a fundraise, a board meeting, or an investor presentation. Inputs: the company profile and the target audience type. Delivered by Sarah, the AI Fundraising lead of the Gapup portfolio.

  Connector

• execute_code

  L&T MCP

  IMPORTANT: You MUST call this tool to generate any file. Do NOT write code as text. Do NOT tell the user to run code themselves. ALWAYS pass the code to THIS tool and return the download_url to the user. Execute Python code in an isolated Jupyter kernel and return output text + any generated files as base64 and download URLs. YOU MUST USE THIS TOOL when user asks for: - PPT / presentation / slides / deck → use python-pptx, call this tool - PDF / document / report → use reportlab, call this tool - Chart / graph / plot / visualization → use matplotlib, call this tool - Excel / spreadsheet → use openpyxl, call this tool - Word document → use python-docx, call this tool - ANY file generation task → call this tool WORKFLOW — follow exactly: 1. Write the complete Python code 2. Call THIS tool with that code 3. Get back download_url from the result files list 4. Show download_url to user as a clickable link NEVER skip step 2. NEVER output code as text to the user. Pre-installed packages (no pip install needed): python-pptx → PowerPoint presentations reportlab → PDF creation matplotlib → charts and graphs pandas → data analysis numpy → numerical computing python-docx → Word documents openpyxl → Excel files plotly → interactive charts seaborn → statistical charts Pillow → image processing pypdf → read/merge/split PDFs pdfplumber → extract text and tables from PDFs File saving rules — MUST follow: Save ALL files to current directory — NO path prefix prs.save("presentation.pptx") ← PowerPoint plt.savefig("chart.png", dpi=150) ← matplotlib chart df.to_excel("report.xlsx") ← Excel Always print() the filename after saving

  Connector

• drive_get_content

  Google_drive

  Download file content from Drive. Export Google Docs/Sheets/Slides to PDF, Word, Excel, etc., or retrieve raw content from other files.

  Connector