Tool search 103,805 tools · 5,318 live servers

Create ONE slide from a structured intent in ONE call: pick a `form` from the menu and put your content in the typed fields (placed on the slide as given), or pass a `brief` and let the server route it. Fields tagged (per-form) bind only where the form has that slot — ignored-with-warning elsewhere; see each form's `binds` in browse_catalog. FORM MENU: agenda_list: an ordered list of sections/topics to walk through bar_rank_chart: bars comparing magnitudes across categories calendar_grid: events on a real calendar - a week planner (day columns x hour axis) or a month grid with release/event chips (data.events) card_grid: several equal, unordered peer blocks (features, options, pillars) case_story: one named story told as evidence: challenge, action, measured result comparison_matrix: options x criteria grid: data.columns x data.rows cycle_flow: a closed loop of ordered stages where the last feeds the first (recurring process) data_table: a plain factual table of records by fields editorial_split: two side-by-side halves in contrast (before/after, problem/solution) funnel: a quantity narrowing through ordered stages gantt_plan: tasks as bars across named periods on a schedule grid gauge_score: one score on a dial against a scale hero_statement: a statement slide: a cover (typographic/image-led/exec-metadata), a from->to or thesis-quote transition, or a contact or next-steps closing hub_spoke: one central element with several elements connected around it kpi_metrics: a board of headline metric cards; add data.sections (Highlights/Risks/Asks) for a one-slide exec summary / board update / QBR snapshot layer_stack: stacked layers where higher sits on, and depends on, lower linear_flow: ordered process stages read left to right (or inputs to process to outputs) maturity_staircase: ascending levels climbing to a higher state nested_magnitude: nested containment - each level contains the next org_structure: a reporting hierarchy / org tree position_map: items placed by two axes - named 2x2 cells or scatter positions pyramid_hierarchy: a triangle of stacked tiers, foundation to apex ramp_curve: a continuous rising wedge split into phases - effort or value accumulating over time section_divider: a section-break slide: big section number + title; blocks = agenda progress chips (emphasis=primary marks the current section) segment_wheel: a wheel of equal segments around a center - peer categories in the round (composition, not flow) status_dashboard: initiatives/workstreams tracked by status, owner, progress strategic_fork: one origin splitting into two mutually exclusive paths, one recommended swimlane_flow: actor/function lanes by phases, task cells, handoffs across lanes swot: the four-quadrant strengths / weaknesses / opportunities / threats grid system_flow_map: nodes connected by directed arrows that carry the message (data/requests move) takeaway_stack: a few bold conclusions, each with one line of support; optional closing ask timeline_roadmap: milestones/phases laid out along a time axis trend_chart: one or more series plotted over time value_chain: support bands over primary activity columns flowing into a goal arrowhead (how value is created; data.support = the bands) visual_showcase: one dominant screenshot/image with numbered callouts pointing into it waterfall_bridge: a start value bridged to an end value by plus/minus contributions Exact per-form data shapes: browse_catalog(type=schema, family=<form>) — the generated, always-current JSON Schema + a worked example. (List-shaped forms take `blocks`: [{"label","sub","detail":[str],"emphasis"}]; structured forms take typed `data`.) Escape modes: mode=code (caller-supplied python-pptx in sandbox, $0.05 — use for forms the menu cannot express: calendars, custom diagrams); mode=status (poll a job, free). Image-led asks (photo covers, full-bleed visuals): hero_statement + image_prompt (+$0.05) or image_src.

高畫質 AI 分析：取得報告截圖圖片（視覺 Bug 用）。⚠ 圖片消耗較高 Token（每張 ~3,000-8,000），建議只在需要看畫面時使用。Report screenshots.

Publish a new project to Shipyard under your account. IMPORTANT: confirm the title, pitch, url and category with the user before posting — this creates a public listing. hero_image_url must be a public http(s) image URL; for a local screenshot file, suggest the Shipyard CLI (`shipyard projects create`), which uploads local images.

FluxInk image text recognition. Extract text from an EXISTING image (file upload, URL, or base64) the user provides. Higher accuracy than built in vision for tightly packed text, multi language documents, math, and LaTeX. Returns per region confidence and detection coordinates. Use this when the user uploads, attaches, or shares an image containing text they want extracted (screenshot, photo, scanned document, receipt, sign, whiteboard, book page, photographed handwritten notes). Use this when the user wants a photographed math expression or chemistry formula converted to LaTeX. Use this when the user references an image and asks to read, transcribe, or digitize the text in it. Do NOT use this when the user has NOT provided an image yet. Do NOT use this when the user wants to draw or handwrite something fresh (call show_handwriting_canvas instead). Do NOT use this when the request is a plain text question, summary, or explanation with no image attached. The language parameter selects the recognition mode. en is English text (default). zh is Chinese text. paddle is multilingual or mixed text. formula is mathematics. latex returns raw LaTeX markup. After returning results, present the extracted text clearly and offer follow up actions like translation, summarization, or editing.

Verify a U.S. physician's medical license status in a specific state. Returns current status (active/expired/suspended/etc.), expiration date, and a confidence indicator. Use this when: - Confirming a physician is currently licensed before scheduling care - Validating credentials during onboarding or recredentialing - Answering 'is Dr. X licensed in [state]?' questions Do NOT use this for: - Bulk verification of >1 NPI — use bulk_verify instead (paid tier) - Historical 'was this physician licensed on date X' — use get_license_history instead (paid tier) Input: NPI (preferred) OR (license_number + state), plus state. State accepts either 2-letter code ('CA') or full name ('California'). A 'not_found' status is a confirmed absence; 'verification_unavailable' means the state board was unreachable (retry — do not treat as unlicensed). Output: status, state, expiration_date, license_active. Paid tiers additionally receive license_number, issuance_date, board_source, last_refreshed_at, screenshot_url for audit-grade primary-source verification. Data is sourced directly from state medical boards and refreshed every 24 hours. Licensy covers all 50 states + DC.

Return an audit-grade screenshot of the state medical board page used to verify a physician's license. The URL is signed and valid for 15 minutes. Use this when: - You need primary-source evidence for an audit, credentialing file, or insurance contract - The end user asks 'where did this come from?' - You're generating a credentialing PDF that needs proof attachments Identify the license by: NPI + state, OR by `license_id` if you already fetched it via verify_license / list_physician_licenses. Free-tier callers receive a structured tier_upgrade_required response. Paid tier (Pro / Enterprise) only.

[Playwright Browser] Take a PNG screenshot of the current page (or a specific element). Returns base64 PNG.