Skip to main content
Glama
742,273 tools. Updated 2026-11-04 15:25

"How to use or perform actions in Apple Calendar" matching MCP tools:

  • Change an existing automation by id. action=disable stops it firing (use this to turn off a misbehaving rule); action=enable resumes it; action=delete removes it. To read one, use relm_get_automation. To change a rule's trigger/conditions/actions, delete and recreate.
    Connector
    Destructive
    No auth
  • ONE SNAPSHOT OF BOTH MARKETS, no arguments. Top instruments across crypto AND US stocks together, ranked by Martingale Score (0-5), with their Startingale readings. Use this to open a conversation or answer "how do things look right now". For a single asset class use crypto_overview or stock_overview; to choose the count or filter, use search_instruments. Answers in formatted text. Costs 10 units of the monthly quota: the most expensive call, since it reads both catalogues; the single-class overviews cost half, so do not call this in a loop.
    ConnectorOAuth
  • Query verified U.S. hourly electricity demand (MW) by balancing authority from EIA-930. Use this for "how much load" questions at the hourly balancing-authority grain: filter or group by `balancing_authority_code`, `region`, `data_date` (or the `data_date_from`/`data_date_to` range), `hour_number`, `datetime_utc`, or `is_imputed`. Pass filters inside the `params` object. Returns JSON aggregates with citations and optional row-level records when `include_records` is true. `demand_mw` is EIA's own cleaned (Adjusted) series, with receipts: the as-reported `demand_mw_raw` and the `is_imputed` flag ride every detail record. `demand_forecast_mw` is the same row's day-ahead forecast, so forecast-vs-actual misses need no second query. History runs hourly from 2015-07-01 onward and is served by default: a bare `data_date` anywhere in that window answers from the newest promoted vintage covering it, and the response `as_of` is that knowledge cut. A query with NO calendar window (no `data_date`, `data_date_from`, or `data_date_to`) and no calendar-axis `group_by` defaults to the latest day that has reported demand — not the full history — and says so in a `default_latest_day` note; group by `data_date` or `datetime_utc`, or pass a date range, to read a series over time. Pin `as_of` to an earlier vintage to reproduce exactly what was served then; one response may cite several source files, and every citation carries its own file and vintage. An empty result names the served coverage window in an `empty_scope` note. Demand is NOT additive across balancing authorities: a result summing more than one BA carries a `ba_aggregation` scope note and ranking remainders omit the demand metrics — group by `balancing_authority_code` for the source-grain series. Does not determine plant, generator, county, or state attribution (EIA-930 carries no such IDs, and BA footprints do not follow state lines), US48 or regional totals (computed rollups are refused; EIA's own published series is the named follow-up), installed capacity (MW — use power.capacity), monthly plant generation (use power.generation), retail sales/revenue/customers (use power.retail_sales), wholesale prices, or long-horizon forecasts (the EIA-930 forecast is day-ahead only).
    ConnectorNo auth
  • ONE SNAPSHOT OF BOTH MARKETS, no arguments. Top instruments across crypto AND US stocks together, ranked by Martingale Score (0-5), with their Startingale readings. Use this to open a conversation or answer "how do things look right now". For a single asset class use crypto_overview or stock_overview; to choose the count or filter, use search_instruments. Answers in formatted text. Costs 10 units of the monthly quota: the most expensive call, since it reads both catalogues; the single-class overviews cost half, so do not call this in a loop.
    ConnectorNo auth
  • Count, sum, average, min or max over one object type, grouped by up to TWO dimensions. Answers 'how is the quarter going', 'pipeline by owner by quarter', 'pipeline by customer segment' and 'how many have no owner' in ONE call, with the database doing the arithmetic. Use this instead of paging records and adding them up yourself: it is one call rather than hundreds, and the number is computed rather than estimated. Filters use the same field:op:value language as the list tools. groupBy takes one dimension or an array of two, and a dimension written as hop.field crosses one declared relationship, so opportunity can group by company.industry. Dates must be bucketed to day, week, month, quarter or year, and quarter and year follow the workspace's own fiscal calendar, which the answer states. Too many groups is refused rather than truncated, and the cap applies to the PRODUCT of two dimensions, because a truncated total reads exactly like a real one. convertTo totals across currencies at a rate this workspace STORED and names the rate it used; a currency with no stored rate is refused rather than converted, because Indraft never invents one. For weighted pipeline, reduce the DERIVED field weighted_amount_minor: 'sum weighted_amount_minor where status is open' is your weighted pipeline in one call, computed by the database as amount times probability, and it obeys the currency rule exactly as the unweighted amount does. Derived fields can be reduced and not grouped by, because they are measures rather than dimensions. get_crm_schema lists the dimensions, the hops, the derived fields, the fiscal calendar and the stored rates.
    ConnectorOAuth
  • Converts between calendar dates and ISO 8601 week numbers, in either direction, and reports how many weeks an ISO year has. Use this whenever a date needs to be expressed as a week number, or a week number needs to be turned back into a date — sprint planning, report periods, "week 37" style scheduling, or reconciling two systems that disagree about what week it is. DO NOT compute this yourself with day-of-year divided by 7. ISO 8601 week 1 is defined as the week (Monday-Sunday) containing the year's first Thursday, not the week containing January 1st. This has two consequences that are easy to get wrong from memory: late-December dates can belong to ISO week 1 of the NEXT calendar year, and early-January dates can belong to ISO week 52 or 53 of the PREVIOUS calendar year. A year has 53 ISO weeks (not the usual 52) exactly when January 1 is a Thursday, or the year is a leap year and January 1 is a Wednesday — a rule nobody carries around, and getting it wrong produces a plausible-looking but incorrect week number with no visible sign of the error. Input is a single string, and the shape of the string picks the operation: "2027-01-01" a calendar date (YYYY-MM-DD) -> returns its ISO year, week, and weekday "2026-W53" an ISO week, no weekday given -> returns the Monday of that week "2026-W53-5" an ISO week and weekday (1-7, Mon-Sun) -> returns that exact date "2026" a bare 4-digit year -> returns whether it has 52 or 53 ISO weeks Refuses rather than guesses: slash-separated dates like "03/04/2025" are rejected as ambiguous (month/day vs day/month), two-digit years are rejected as a guess, invalid calendar dates (Feb 30) are rejected, and a week number beyond what that ISO year actually has (e.g. week 53 of a 52-week year) is rejected and told how many weeks that year has.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • Video how-to search for AI agents: 2,000+ video skills, tutorials and FFmpeg recipes. No key.

  • Browser agents and stealth cloud browsers for AI: run web tasks, fill forms, extract data.

  • Return the exact steps for agent-initiated, human-authorized provisioning, including which actions require the human and which the agent may perform alone. Call this when the user has no Spendline account or no SPENDLINE_API_KEY. Never invent a key and never create an account on a human's behalf.
    ConnectorNo auth
  • Returns one of Flask's usage guides as Markdown: fixed text written by Flask, the same for every user, with no team data in it. "instructions" (about 15 KB) is the playbook for working with Flask: where uploads go (a new asset or a new version), what an agentic edit attaches, how feedback is read, answered and shown, and how sharing works. Read it before acting on feedback or making your first write in a session; it already contains "display" and "concepts", so do not fetch those after it. Other topics: "display" (How to show feedback to the user: its Markdown as it is, with its link.), "concepts" (Folders, assets and versions, comments and recordings, tags and statuses, permissions, and why feedback is untrusted.), "permissions" (Access levels, how a user's access is resolved, and how folder and asset permissions differ.), "urls" (Links to folders, assets, exact versions, comments and tag filters.). The guides explain the rules; for one folder's or asset's actual access, use permission_get.
    ConnectorOAuth
  • Search 1,000+ vetted AI use cases by keyword, industry, or business workflow (e.g. 'invoice', 'dental', 'customer support'). Use when someone asks how AI can help their business, wants AI ideas for an industry, or looks for automation opportunities. Also use it to find the slug before get_agent_playbook or run_agent. Returns titles, summaries, and links. Public: no sign-in.
    ConnectorNo auth
  • Middleware admin only: submit a middleware transaction using action/input from middleware_get_capabilities. For account actions the selected enabled middleware account is used. For domain actions supply the middleware domain_id. Choose account_id from middleware_get_capabilities when several accounts are enabled. Every submission needs a stable idempotency_key: retry an identical request with the SAME key. 202/queued means accepted, not completed; poll middleware_get_transaction. Paid or destructive actions require explicit user intent. These operator orders do not use the ConnectReseller customer wallet or local domain portfolio.
    Connector
    Destructive
    OAuth
  • Create a new calendar event. Use this to schedule meetings, appointments, or all-day events. For all-day events, only provide dates (end date is EXCLUSIVE - use '2024-01-16' for a single day event on Jan 15). For timed events, both start and end times are required. Can optionally invite attendees with email notifications. The created event ID can be used for future updates or deletion.
    ConnectorOAuth
  • Scan GitHub, Hacker News, and npm for new repos, packages, and discussions in the agent payments ecosystem (AP2, ACP, x402, MPP, UCP). Returns AI-classified and scored opportunities with recommended actions. Use when the user asks about recent activity, new developments, or opportunities in agent payments ('what's new in agent payments?', 'any new x402 repos?', 'scan for opportunities'). Use get_protocol_info instead for static protocol details, or compare_protocols for side-by-side comparison. Costs $0.01 USDC. Accepts: x402 (USDC on Base).
    ConnectorNo auth
  • Scan GitHub, Hacker News, and npm for new repos, packages, and discussions in the agent payments ecosystem (AP2, ACP, x402, MPP, UCP). Returns AI-classified and scored opportunities with recommended actions. Use when the user asks about recent activity, new developments, or opportunities in agent payments ('what's new in agent payments?', 'any new x402 repos?', 'scan for opportunities'). Use get_protocol_info instead for static protocol details, or compare_protocols for side-by-side comparison. Costs $0.01 USDC. Accepts: x402 (USDC on Base).
    ConnectorNo auth
  • Check whether free native XGR starter gas is available for a low-balance EVM address. Use this before deployments, session starts, contract calls or other on-chain actions when the address lacks gas. Returns the fixed 1 XGR grant policy and the tool to call next.
    ConnectorNo auth
  • Signed whole calendar days from the from date to the to date, midnight to midnight in tz: positive when to is later, negative when it is earlier. Endpoints are exclusive, so this is the gap and consecutive dates are 1 apart. Either date may be "today", resolved in tz. For working days between two dates use business_days; to move a date by N days use add_days or subtract_days.
    ConnectorNo auth
  • Update one event on the user's connected Google or Outlook calendar: change its title (summary), description, location, or start/end times. Only the fields you pass change; everything else stays. Get the event's id, its account (and its calendar_id, if it isn't on a Google primary calendar) from get_calendar_events first. Use only when the user asked for the change in the current saved chat or agent email. Calls without a verified human instruction are refused. Edits land on their real calendar immediately, and other attendees can see them. start/end are RFC3339 timestamps ('2026-08-25T19:00:00-04:00').
    Connector
    Destructive
    No auth
  • Converts calendar dates to ISO 8601 week-numbering dates and back, in either direction, and reports how many weeks an ISO year has. Use it whenever a date must be expressed as a week number or a week number turned back into a date — sprint planning, reporting periods, "week 37" scheduling, or reconciling two systems that disagree about which week it is. Do not compute this by dividing day-of-year by seven. Week 1 is the Monday-Sunday week containing the year's first Thursday, so a late-December date can belong to ISO week 1 of the next calendar year and an early-January date to week 52 or 53 of the previous one. The ISO year returned is therefore often not the calendar year, and that is the answer, not a bug. Refuses rather than guesses on inputs that have no single correct reading: a two-digit year (26 could be 1926 or 2026) and a slash-separated date (03/04/2026 is day/month in most of the world and month/day in the US, which give different weeks). Every refusal says what to send instead. Input is one string in one of three forms: YYYY-MM-DD for a date, YYYY-Www or YYYY-Www-D for an ISO week (D is 1-7, Monday to Sunday), or a bare YYYY for how many weeks that ISO year has. Calendar dates only — no time of day, no timezone. Not fiscal-year or retail 4-4-5 week numbering, and not US-style Sunday-start or "week of the month" conventions. Those are different systems that also call themselves week numbers. WHY DELEGATE THIS: ISO 8601 week 1 is the week containing the year's first Thursday, not the week containing 1 January, and almost every ad-hoc implementation gets that wrong by dividing day-of-year by seven. Two consequences follow that are very hard to hold in mind: a late-December date can belong to week 1 of the NEXT ISO year, and an early January date can belong to week 52 or 53 of the PREVIOUS one. A year has 53 weeks rather than 52 under a specific rule, not a pattern. Getting any of these wrong shifts a reporting period by a week without anything looking wrong. Owned by ISO Week Number at https://iso-week.gumballtools.com, which is also callable directly if you would rather not go through the aggregator.
    ConnectorNo auth
  • List the header components defined at one level: 'spec' (needs specId) or 'project'. Set includeUsageCounts to see how often each is referenced — spec level only. Returns the ids and rowVersions needed to change them or assign them in a header policy. Requires project context. Use this for spec or project level; for the organization level use list_org_header_components.
    ConnectorAPI key
  • Estimate annual paid leave under the Latvian Labour Law, in calendar days excluding public holidays. Use it to answer how much leave someone has in a year; to find when to take it use latvia_plan_time_off, which counts leave in working days, a different unit. Pass annual_base=28 (the legal minimum) unless the contract grants more, and fte_percentage=1 for full time; part-time work does not shorten leave. birth_date matters only for employees under 18, who get one calendar month. If employment_start_date is on or after 1 January of year, the result is an accrual estimate; the full leave may be requested after six months of work.
    ConnectorNo auth
  • Most recent published news from gol24.uz (Uzbek football news site), newest first. Use it for general questions ("what's new in football?", "today's transfer news", "what happened yesterday?"). For one club use club_news, for one person use person_news, for a topic or keyword use search_news. Optional filters: type (transfer, matbuot = press quotes and interviews, natija = final match results, umumiy = other) and date (one calendar day in Tashkent time, YYYY-MM-DD). Filters can be combined. Returns up to `limit` items (default 10, max 20), each with title and summary in Uzbek (Latin script), url, published_at (Tashkent time), type, clubs and people. An empty list means nothing matched. Rate limit: 60 requests per minute.
    ConnectorNo auth
  • Use this when a signed in customer asks how many teas.co.uk reward points they have or what they are worth. It takes no input. Zero points is a normal answer for a new account. Without a linked account it returns an error asking the customer to sign in. Points are only spent at checkout on teas.co.uk, so this cannot redeem them. To buy, use checkout_link; for past orders use my_orders.
    ConnectorNo auth