Skip to main content
Glama
807,599 tools. Updated 2026-11-19 18:18

"iPhone 16e camera review summary and table creation in Italian" matching MCP tools:

  • One-shot convenience tool: starts a blueprint run and polls until it completes, fails, or pauses for review. Returns the final run with `output_url` (or `outputs` [{label, url}] for multi-output blueprints — prefer `outputs` when present). Download URLs are signed with a 10-minute TTL; re-fetch with get_blueprint_run for fresh links. NOTE: caption-video pauses in status awaiting_review — this tool then returns early with `awaitingReview: true` and the run's `srt_text`; review/edit the transcript and resume with continue_blueprint_run. If your MCP client enforces a short per-request timeout (many default to 60s), use run_blueprint + get_blueprint_run polling instead. Per-blueprint input fields (* = required): - product-ad: logo_url*, photo_url*, music_url? — GENERATIVE, costs 200 tokens - caption-video: video_url*, language?, style? (bold-bottom|clean-lower|center-pop|top-title) — pauses at awaiting_review with srt_text for transcript review; resume with continue_blueprint_run - viral-short: video_url*, hook_text*, style? (top-hook|center-statement|bottom-caption|lower-left), music_url? - quote-card: quote*, name?, handle?, photo_url?, output? (video|image) - watermark: video_url*, logo_url*, position? (top-left|top-right|bottom-left|bottom-right|center), size? (small|medium|large) - resize-format: video_url*, format? (9x16|1x1|16x9|4x5), fit? (pad|crop) - zoom-in: video_url* - zoom-out: video_url* - camera-glide: video_url*, direction? (right|left) - boomerang: video_url* - speed-changer: video_url*, speed? (0.5|1.5|2|4) - video-to-gif: video_url*, length? (5|10|15), size? (480|640), caption?, caption_position? (bottom|top|center) — output is a .gif - product-slideshow: photo1_url*, photo2_url*, photo3_url?..photo5_url?, music_url?, aspect? (9x16|1x1|16x9) - listing-kit: video_url* — multi-output (4 platform variants in `outputs`) - hook-variants: video_url*, hook1*, hook2?, hook3?, ratio? (9x16|4x5|1x1|original), style? (top-hook|center-statement|bottom-caption) — multi-output (one per hook in `outputs`) Input URLs: public https or upload-bucket gs:// (use request_upload_url + confirm_upload to get one). FFmpeg-lane blueprints charge no tokens (they meter plan compute minutes); only generative blueprints (product-ad) charge tokens.
    ConnectorOAuth
  • Parse a Primavera P6 XER file and return a TABLE SUMMARY (not the full row-level data — XER row dumps explode the MCP context window). For each table in the XER, returns the table name, field list, and record count. Per-row data is intentionally omitted — for forensic / DCMA / windows analysis use the dedicated tools (``forensic_windows_analysis``, ``critical_path_validator``, etc.) which consume the parsed XER internally and return analytical summaries, not raw rows. Use this tool to confirm an XER is parseable, list its tables, see the data date / project name from PROJECT, or count activities in TASK before deciding which deeper tool to run. Args: xer_path: server-side filesystem path to the XER file. xer_content: full text of the XER file (alternative for hosted/remote use). Supply EXACTLY ONE of path/content. Returns: { "filepath": absolute path, "encoding_used": "utf-8" | "cp1252" | ..., "ermhdr": file header dict (P6 version, export user, etc.), "tables": [{"name", "fields", "record_count"}, ...], "table_count": int, "total_records": int, "project_summary": { "proj_id", "proj_short_name", "proj_long_name", "data_date", "plan_end_date" } (from first PROJECT row, if any) }
    ConnectorNo auth
  • Capability manifest of the hosted runners: LAMMPS version, installed packages, and every style by category with gpu=true (KOKKOS-accelerated) or gpu=false (exists, but runs on the pod's CPU cores at the GPU rate). Default = compact summary; runner=lammps&full=true returns the whole style table. Use preflight_deck to check a specific deck.
    ConnectorNo auth
  • The full public document for one dataset as Markdown: summary, facts, access instructions, and every table with its columns, types, descriptions and units. No account needed. Example: {"id": "kden-metar-hourly"} — the `id` is a slug from search, and a canonical dataset URL works too. Returns {id, title, text, url, metadata: {slug, publisher, published_at, table_count, topics}}. publisher is the account that published the dataset, not the source it was gathered from. Cite the dataset by `url`. For machine-readable table ids and schemas, call get_dataset and get_table_schema instead.
    ConnectorNo auth
  • Replace the design's camera moves and morphs between layers with a value in the stored format (read the current one with get_design timeline); `{}` clears it. A `flow` alone (slides in order, joined by transitions) is compiled into the camera and morphs it plays. Validated before saving, and the timeline grows to fit. Returns the timeline. Saved as a new revision that undo reverts; if any part is refused, nothing changes. Use it to edit or clear choreography as a whole; for one camera move use camera, for a single layer's motion animate, for a wipe between scenes make_transition, and for the length set_timeline.
    ConnectorOAuth
  • Parse a Primavera P6 XER file and return a TABLE SUMMARY (not the full row-level data — XER row dumps explode the MCP context window). For each table in the XER, returns the table name, field list, and record count. Per-row data is intentionally omitted — for forensic / DCMA / windows analysis use the dedicated tools (``forensic_windows_analysis``, ``critical_path_validator``, etc.) which consume the parsed XER internally and return analytical summaries, not raw rows. Use this tool to confirm an XER is parseable, list its tables, see the data date / project name from PROJECT, or count activities in TASK before deciding which deeper tool to run. Args: xer_path: server-side filesystem path to the XER file. xer_content: full text of the XER file (alternative for hosted/remote use). Supply EXACTLY ONE of path/content. Returns: { "filepath": absolute path, "encoding_used": "utf-8" | "cp1252" | ..., "ermhdr": file header dict (P6 version, export user, etc.), "tables": [{"name", "fields", "record_count"}, ...], "table_count": int, "total_records": int, "project_summary": { "proj_id", "proj_short_name", "proj_long_name", "data_date", "plan_end_date" } (from first PROJECT row, if any) }
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    A
    quality
    B
    maintenance
    Lets AI agents see and control a real iPhone over USB or Wi-Fi through WebDriverAgent: screenshots in tap coordinates, UI tree, taps, swipes, typing, buttons, apps and URLs. Keeps the screen awake during sessions; runs on macOS, Linux and Windows.
    19
    GPL 3.0

Matching MCP Connectors

  • Get Lenny Zeltser's expert CTI writing guidelines. Topics include tone, words, structure, executive_summary, voice, articles, summary, brief (one-page brief section guidance), handoffs (cross-server routing), methodology (the three subsections), fields (per-field guidance), and CTI-specific topics: attribution (full Six Signals prose), confidence (ICD-203 ladder), pyramid_of_pain, six_signals (signals table only), and anti_patterns. The general writing topics (tone/words/structure/executive_summary) now defer to `get_security_writing_guidelines` for the canonical Five Elements rules; CTI-specific content lives in the other topics. Pair the 'fields' topic with field_id for single-field guidance. This server never requests your campaign or threat-intel notes and instructs your AI to keep them local—templates and guidelines flow to your AI for local analysis.
    ConnectorNo auth
  • Translate a plain-language question into a candidate SQL query using pattern-matching against the live schema (no AI model — simple questions only: counts, averages, filtered selects on a named table). Returns the SQL without executing it, with a confidence score; low confidence means the table was guessed. Review the statement and tables_used, then run it with scalix_db_query. For complex questions, read scalix_db_schema and write the SQL directly.
    ConnectorNo auth
  • Mint cryptographically-random identifiers using the platform CSPRNG — the correct source for IDs that must be unpredictable, unlike model-generated values. type selects the format: uuid_v4 (random, the default), uuid_v7 (time-ordered, sortable by creation), or ulid (26-char Crockford-base32, lexicographically sortable). Set count to mint a batch in one call (up to 1000); the returned ids array always contains exactly count values and is never truncated. For uuid_v7 and ulid, a batch is monotonic — strictly increasing even within the same millisecond — so the ids array stays in sorted creation order; ids minted in the same millisecond are separated by random gaps, so no id in a batch can be derived from another. IDs from this tool feed into toolkit_generate_qr (pass ids[0] as data) to create a scannable code.
    ConnectorNo auth
  • [~] PRIORITY TRIGGER: Use this tool when user mentions 'PR', 'Pull Request', 'list PRs', 'show PRs', 'active PRs', 'mes PR', 'liste des PR', 'pull requests ouverts', 'what PRs are open', 'PRs by [author]', 'PRs targeting [branch]'. NEVER call search_d365_code for PR listing requests. List Pull Requests in an Azure DevOps Git repository. If `repositoryId` is unknown, omit it and all repositories will be listed first. Filters: status (Active/Completed/Abandoned/All), author display name, target branch. Returns: PR ID, title, author, source->target branch, review status, linked work items, creation date. Use `ado_analyze_pr_impact` with a PR ID to get full D365 code impact analysis. Requires DEVOPS_ORG_URL + DEVOPS_PAT (Code: Read scope).
    ConnectorNo auth
  • Lists French legal units created in a requested date window using the official historized Sirene source. Use when: You need French legal units created during a recent or historical date window. Avoid when: You need BODACC publication events rather than Sirene creation dates; use company/fr/events or legal-announcements-search. Limitations: Creation date is the Sirene legal-unit creation date and is not the same as a BODACC publication date. The requested window is limited to 366 days per call. A cursor is bound to its date-window query and should only be reused to continue that same query. Price: 0.010 USD per call via x402. Paid-call behavior: source records are not modified, but a successful invocation can consume the advertised x402 payment; the payment-required challenge is free, and repeating the tool after a completed paid invocation may require a new payment. Accepted x402 networks: eip155:8453, xrpl:0.
    ConnectorNo auth
  • Use when the user asks to inspect, summarize, or visualize an attached TFLite, ONNX, GGUF, SafeTensors, Core ML, or ExecuTorch deployment artifact. Opens a browser-local analyzer, returns a hash-bound format-neutral Model IR table and static evidence summary, and provides deterministic document views without executing model code. Do not use for training checkpoints, measured latency, task accuracy, clinical validity, regulatory compliance, or actual runtime placement.
    ConnectorNo auth
  • Successful automatic poses now continue without review, including imports. Four-direction setup stays automatic and eight-direction keeps its existing selection. Imported generation preserves source rendering rather than project style. Use this tool only when get_job returns a pending automaticPoseFallback. If poseReview is present, this is a historical imported-pose checkpoint from an earlier flow: show originalUrl and poseUrl side by side and ask the user to check style, complete head/body and unwanted ground/scenery. Submit choice="generated" only after they accept that exact pose, or choice="original" to use their original character; include poseVersion from poseReview.version. Use cancel_job to cancel. Without poseReview, pose creation failed: ask whether to continue with the default pose or cancel, and use choice="original" to continue. Never approve automatically. Both choices resume the original approved animation request at normal video cost. Accepted generated poses are reused without another review until regenerated.
    ConnectorNo auth
  • Change PART of a project's schema without dropping any of it (saves to database, does NOT deploy). Send only the change. The server applies it to the saved schema, in order and all together, and keeps every table and field it does not touch — including their identity, so a rename stays a rename and the column keeps its data. OPERATIONS (each one small object, applied in the order given): • {"op": "add_table", "table": "clocks", "definition": {...}} new table, same FLAT rules as create_project • {"op": "rename_table", "table": "clocks", "to": "timers"} • {"op": "add_field", "table": "assets", "field": "serial", "definition": {"type": "string", "max_length": 64}} • {"op": "rename_field", "table": "parameters", "field": "is_clock", "to": "clock_kind"} • {"op": "set_field", "table": "assets", "field": "name", "properties": {"max_length": 300}} merges; a property set to null is removed • {"op": "set_table", "table": "assets", "properties": {"__audit__": true}} __policy__, __constraints__, __audit__, __admin_write__ Dropping a table or field is drop_schema_items, a tool of its own. ALL OR NOTHING: an operation that cannot be applied — a table or field that is not there, a name already taken, a schema the deploy would refuse — refuses the whole patch, naming the operation, and nothing is saved. EVERY ANSWER IS A DIFF: 'applied' (what each operation did), 'diff' (every changed property by path), 'summary' and 'plan' (the migration a deploy would then run), and 'version' (the schema's version after the change). WORKFLOW: 1. get_schema with tables/fields to read the part you are changing (its 'version' is the whole schema's) 2. preview_schema_change with the operations: check 'diff' and 'plan' 3. patch_schema with the same operations (pass expected_version to be refused if someone else saved meanwhile) 4. deploy_staging, then get_job_status
    ConnectorNo auth
  • Change PART of a project's schema without dropping any of it (saves to database, does NOT deploy). Send only the change. The server applies it to the saved schema, in order and all together, and keeps every table and field it does not touch — including their identity, so a rename stays a rename and the column keeps its data. OPERATIONS (each one small object, applied in the order given): • {"op": "add_table", "table": "clocks", "definition": {...}} new table, same FLAT rules as create_project • {"op": "rename_table", "table": "clocks", "to": "timers"} • {"op": "add_field", "table": "assets", "field": "serial", "definition": {"type": "string", "max_length": 64}} • {"op": "rename_field", "table": "parameters", "field": "is_clock", "to": "clock_kind"} • {"op": "set_field", "table": "assets", "field": "name", "properties": {"max_length": 300}} merges; a property set to null is removed • {"op": "set_table", "table": "assets", "properties": {"__audit__": true}} __policy__, __constraints__, __audit__, __admin_write__ Dropping a table or field is drop_schema_items, a tool of its own. ALL OR NOTHING: an operation that cannot be applied — a table or field that is not there, a name already taken, a schema the deploy would refuse — refuses the whole patch, naming the operation, and nothing is saved. EVERY ANSWER IS A DIFF: 'applied' (what each operation did), 'diff' (every changed property by path), 'summary' and 'plan' (the migration a deploy would then run), and 'version' (the schema's version after the change). WORKFLOW: 1. get_schema with tables/fields to read the part you are changing (its 'version' is the whole schema's) 2. preview_schema_change with the operations: check 'diff' and 'plan' 3. patch_schema with the same operations (pass expected_version to be refused if someone else saved meanwhile) 4. deploy_staging, then get_job_status
    ConnectorNo auth
  • List Push Notification history for the account, newest first. Use it to review what was sent, find a notification's public_id, or filter by Tags; for one known notification, use get_push_notification. Equal creation times use descending ID order. Defaults: limit 50, offset 0; maximum limit 100. Continue with meta.next_offset and the same filters; stop when it is null. Results can change between requests.
    ConnectorOAuth
  • List Live Activities sent from this account, newest first, with their status, Tags, and latest content. Use it to review recent activity or find an activity_id; for one known activity, use get_live_activity. To change a running activity, use the stream tools such as set_live_activity_stream. Equal creation times use descending ID order. Defaults: limit 50, offset 0; maximum limit 100. Continue with meta.next_offset and the same filters; stop when it is null. Results can change between requests.
    ConnectorOAuth
  • Files the company with its formation state through doola's registered agent and emails the responsible party what they must sign: the SS-4, plus Form 8821 for Expedited EIN, or nothing when the responsible party's SSN lets doola apply for the EIN online. Filing cannot be undone. Call it ONLY after presenting a complete summary table of everything collected and the user explicitly replied 'submit', with {userConfirmed: true}. Refused with PRECONDITIONS_NOT_MET, listing `missing`, while any earlier step is incomplete. Formation flow, in order: start_formation, create_checkout_session, verify_payment, save_company_details (industries from search_industries), submit_formation. Each response's nextStep is the step the flow now waits on.
    Connector
    Destructive
    OAuth
  • Reads the yearly series of nights and arrivals of one Italian comune, split by guests resident in Italy and abroad. Use it for the trend of one comune; do not use it for one year, capacity or population (use leggi_dati_comune instead) or several comuni (use confronta_comuni instead). `cod_istat` comes from cerca_comune; `da_anno` and `a_anno` are inclusive, and without them all years come back. From 2025 ISTAT counts include privately rented flats, so totals across that year are not comparable: `anno_discontinuita` flags it. A comune without figures gets an empty list in `serie` and a `nota`, not an error. An unknown code or a range fully outside its years is an error saying what to pass. Public, no authentication; 30 requests per minute per client, shared across tools.
    ConnectorNo auth
  • Lists the venues in an Italian province where an event is currently scheduled, with the available versions (e.g. original language, 3D) and a link for each. Use it for 'where can I see X in Milan' and, passing venueId, for 'I want to see X at cinema Y': the response then contains the direct webtic.it link to give the user. If the event is not scheduled at that venue, the response says so and lists the other venues in the same province where it is. This data says what is currently on sale, not when: dates, showtimes and prices are not available here and are shown on the webtic.it links.
    ConnectorNo auth
  • Create a receipt to verify a message your runtime already posted. Supply its same-site HTTPS post_url and the receipt_code from dry_run_post; never supply a publishing URL. Use dry_run_post before posting. Creation saves a receipt, reads the page subject to robots.txt, and returns a token once. Recheck using receipt_id and receipt_token with slug. A robots refusal or missing code does not prove posting failed. Repeated creation can create duplicates; SwarmIndex never posts.
    ConnectorNo auth