Skip to main content
Glama
667,139 tools. Updated 2026-10-16 23:33

"Creating an application" matching MCP tools:

  • Call this first for every XGR purchase. Read live price, stock and payment assets; use payment_assets[].key exactly as payment_asset and inspect requires_sender_wallet before creating an order.
    ConnectorNo auth
  • Submit an artist's application for Dynamoi music distribution after the user explicitly asks to apply and all five eligibility requirements are met. This records an application for manual review; it does not approve distribution, accept an agreement, submit a release, transfer rights, configure splits or tax forms, or deliver music to stores. All three valid ISO 3166-1 alpha-2 country or territory codes, an adult signer attestation, confirmApplicationSubmission=true, and a concise userIntentSummary are required. Country, tax, payout, sanctions, and provider-delivery checks remain manual progression gates after intake; a valid code does not imply approval. Repeated submission is idempotent for an active application.
    ConnectorNo auth
  • List user's guides Returns a list of guides for the authenticated user. Use `query` to check whether a guide already exists before creating one (creating a duplicate costs credits). Beware of two behaviours of this endpoint: - `query` and `group` are case-insensitive REGULAR EXPRESSIONS, not exact matches: special characters in the value are interpreted as regex syntax, and an invalid regex returns no result at all. (`status` is different: a known status is matched exactly, any other value falls back to a regex.) Always compare the returned `query` and `source` yourself, and fall back to an unfiltered paginated scan before concluding that nothing exists; - `totalCount` does NOT take `query` nor `group` into account (known limitation: both are applied as application-level regexes that the count query does not know, so it returns 0 as soon as either is used, alone or combined with `status`). Filtering on `status` alone does give a correct `totalCount`, since it is a real stored field. For an existence check, trust the `guides` actually returned; `totalCount` is only reliable for paginating a listing filtered by `status` alone, or not filtered at all. An empty result is returned as a 404 with `success: false` and `error: "No guides returned"`, not as an empty list.
    ConnectorNo auth
  • Submit an application to the 20-person spatial-computing beta. WRITES a real application under a real person's name and commits them to a 5-week in-person NDA-bound program, so CONFIRM EVERY ANSWER WITH YOUR HUMAN FIRST and never invent one on their behalf - particularly the NDA, commitment and in-person answers, which are promises they have to keep. Call ic_spatial_beta_program first for the catalog and the exact allowed values. One application per email address; a second is refused rather than silently merged. The response carries a `claim_token` shown EXACTLY ONCE: surface it to your human verbatim, because without it an applicant with no IC account can never read their own status again. No auth required; a token only attributes the application. Returns: { ok, application_id, claim_token, status, failed_gates, cohort, message }.
    ConnectorNo auth
  • Connect a Tribute account to the application or change the connection. Requires manage_settings. Pass at least one field; they are applied in the order apiKey, notificationsConfirmed, paused. Returns the same view as get_tribute_setup. The API key is stored encrypted and no tool returns it. Three things happen in the owner's Tribute account and no tool can do them: creating the API key, creating a digital product and getting it approved by Tribute, and saving the notification link in Tribute (Dashboard → Settings → API Keys → Webhook URL).
    ConnectorNo auth
  • START contact with the owner of a Teppek LISTING on the user's behalf (identified by the listing) — the primary FIRST-CONTACT path (there is no price-offer/accept/reject flow). Opens a private thread with the owner; contact routes through Teppek and never exposes raw personal details. To continue a thread that already EXISTS (you have a thread_id from list_conversations), use reply_to_conversation instead. External-feed listings (e.g. imported jobs) have no Teppek owner, so this returns a redirect to the external application URL instead of creating a thread. Requires the user to be connected to Teppek: an anonymous call returns an AUTH_REQUIRED error with an authorize_url — surface 'Connect with Teppek' to the user, then retry.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • Track every document added or changed in one RIS application within an exact date window (changed_from/changed_to), optionally including deletions (include_deleted) — the delta-sync and monitoring primitive for mirrors and watchers, and the only surface that reports removals. Unlike the search tools’ coarse, additive-only changed_since intervals, this is exact-dated and deletion-aware. application accepts every RIS application code listed by ris_list_reference topic applications, including BrKons, LrKons, Dsk, and BgblAuth. Each changed document comes back in a compact cross-class record — document_number (for ris_get_document), title, dates, binding_status, and rendition URLs — plus its last-changed date; removed documents come back as deleted records with a deletion timestamp. One application per call; page explicitly for large windows.
    ConnectorNo auth
  • Attach a markdown company analysis (research you produced) to an application. Single document per application — a new call REPLACES the previous one. Max 100000 bytes (~100 KB) of utf-8. The user reads it in the dashboard, e.g. before an interview. Example: `attach_analysis({application_id: "…", markdown: "# Bosch\n\n## Culture…"})`.
    Connector
    Destructive
    No auth
  • Start a PDF upload. Returns {upload_id, put_url, expires_at, max_bytes}. HTTP PUT the raw PDF bytes to put_url (Content-Type: application/pdf, no auth needed — the URL is signed). The PUT response includes the validation report. Then pass upload_id to create_order. Keyless use is bounded per calling origin: 20 create_upload calls per hour, at most 5 unused uploads open at a time, and put_url expires in 2 hours — so PUT the bytes promptly and reuse an upload_id you already hold instead of creating extras. An API key (see apply_enterprise) lifts both limits.
    ConnectorNo auth
  • Only for the Awning team. approve publishes the business; reject needs a note the owner will see. To approve an application of any route but rename, pass expected_name: the business's name exactly as op_applications showed it to you (business.name). The owner can change the name while the application waits, so approving is refused when the business is called something else now: list the applications again, check the name, then decide. For route rename, approve gives the business the new name from the request and changes nothing else (no expected_name needed), and reject keeps the current name. recall applies to an approved application with route auto_branch — a new location that went live without review: it leaves the catalogue and returns to the queue as a new application.
    Connector
    Destructive
    No auth
  • Approve or reject one course application from application_list. Approving ENROLLS the applicant right away (prerequisites skipped, the course's access period applied) and emails them an approval with a link into the course; rejecting records the decision and emails them your decisionNote, enrolling no one. Repeating the decision an application already has does nothing (no second enrollment or email), and rejecting an application that was already approved does not remove the enrollment: use enrollment_revoke for that. To enroll someone who never applied, use enrollment_create. Returns {id, status, decisionNote, reviewedAt}.
    ConnectorAPI key
  • List all fixed tax rates configured for this Checkout Page account. Use this tool to find an existing tax rate before creating a new one or when setting up a page with `tax.mode: "fixed"`. Check whether a suitable rate already exists — avoid creating duplicates. This tool returns all rates — there is no filtering or pagination.
    ConnectorOAuth
  • Reports which governance policies an application would pass or fail for an environment. Send `manifest` (YAML or JSON) to validate a document without creating anything. Call this before springroll.deploy to avoid a rejected submission. Read the `springroll://manifest/example` resource for the document's shape. Send `application` instead to explain why an existing application cannot deploy or promote to `environmentType`, with specific remediation for each failing rule. Call this when a deployment is rejected with POLICY_BLOCKED. Send exactly one of the two.
    ConnectorNo auth
  • Where one application stands. Needs BOTH the application_id and the claim_token returned at submission: an id alone returns only public slot counts and never anyone's record, because ids travel through URLs and chat logs and must not work as credentials. A wrong or missing token is answered exactly like an unknown id, so this cannot be used to test whether an id exists. Args: { application_id, claim_token }. Returns: { ok, found, application?, cohort }. No auth required.
    ConnectorNo auth
  • Read personalized curated jobs with reasons, missing facts and application status. Start here for recommendations. Returns at most 20 matches per page in ranking order; while next_cursor is not null, call again with cursor set to it for the next page. Includes profile completeness and a retry hint while awaiting the first match computation. Never starts an application or edits the profile.
    ConnectorOAuth
  • Read a form's questions before collecting answers or creating an application. Each question has id (the answer key for update_application), label in the form's own wording, type, choices, required, conditions (shown_when: asked only when that holds) and approx_max_chars (keep text within it). Also returns sections, provenance with the official source_url, limitations, and blank editable and sample PDF links. Long forms are paged: read the sections list, then pass section and/or offset for the rest. Read-only; it does not create anything.
    ConnectorOAuth
  • Business — Change what an application in progress fills in, without stopping it. Use when the user says something about an application Worklittle is filling right now ("say my notice period is one month", "my friend Ana Ruiz referred me", "I need visa sponsorship for the US", "make that answer shorter"). Pass their wish as plain instructions with their exact facts; never add facts. Works while the application is running, ready to submit, or waiting for answers. Needs the session_id from apply_for_job or list_active_applications. For facts that should apply to every future application too, also call save_about_me.
    ConnectorNo auth
  • Approve an open application: the entry is created live from its proposal, your assessment (as it stands, with any field given here changed) is recorded with it, and the applicant is emailed. The dry run warns when the assessment falls short of the policy or an entry already links its Wikidata item. Never your own application unless you could create that entry directly. Audited. Dry run by default.
    Connector
    Destructive
    OAuth
  • Read the Tribute one-time payment setup of an application: whether a Tribute account is connected, the notification link and whether the owner confirmed it, the products set up here, the number contact variables a purchase can add to, and nextSteps (what is still missing, in order; empty means ready to sell). Read-only; requires manage_automation. Start here for anything about Tribute. Three things happen in the owner's Tribute account and no tool can do them: creating the API key, creating a digital product and getting it approved by Tribute, and saving the notification link in Tribute (Dashboard → Settings → API Keys → Webhook URL).
    ConnectorNo auth
  • Create a new data source for the authenticated application. The 'settings' object must match the given 'type'. Returns the created data source. Creating a data source does not sync any content — use run_data_source to start a sync.
    ConnectorNo auth
  • Create a new data source for the authenticated application. The 'settings' object must match the given 'type'. Returns the created data source. Creating a data source does not sync any content — use run_data_source to start a sync.
    ConnectorNo auth