Skip to main content
Glama

Provision Resource

provision_resource

Provision a Floot-managed backend resource for the project, fully server-side (Floot mints the secrets), and seed the working code for it. Idempotent: re-running returns the existing resource and skips seed files that exist. Available:

  • database — A Floot-managed Postgres database (Neon). FLOOT_DATABASE_URL is set for the app.

  • auth — Email/password + session auth (JWT_SECRET, auto-provisions a database if none). Injects auth pages, endpoints, and helpers.

  • oauth-login — Sign in with Google via Floot's brokered OAuth (FLOOT_OAUTH). Injects OAuth provider classes, login buttons, helpers.

  • microsoft-login — Sign in with Microsoft via Floot's brokered login (FLOOT_MICROSOFT_LOGIN). Injects button + auth endpoints.

  • google-integration — Built-in Google integration (FLOOT_GOOGLE_INTEGRATIONS): end users connect their Google account so the app reads/writes their Gmail, Calendar or Drive, unless the user wants their own Google client. See get_guides("floot-provided-google-integrations").

  • microsoft-integration — Microsoft Graph access (Outlook/Teams/etc.) via Floot's brokered Microsoft OAuth (FLOOT_MICROSOFT_INTEGRATIONS). Injects Connect button + endpoints.

  • push-notifications — Web + native push (FLOOT_PUSH). Mints VAPID keys, injects helpers/pushClient (subscribe/unsubscribe) + a service worker.

  • self-edit — Lets the app edit ITS OWN source through the Floot MCP server (FLOOT_SELF_EDIT): mints a project-scoped bearer token, exposed to the backend as FLOOT_PROJECT_TOKEN + FLOOT_PROJECT_ID. Duplicates get their own token. No seed code — see get_guides("floot-self-edit").

  • payments — Built-in payments (FLOOT_PAYMENTS), unless the user wants their own Stripe account. See get_guides("floot-payments").

  • shipping — Shipping physical goods through the owner's own Shippo account (FLOOT_SHIPPING: rates, labels, tracking); the preview uses built-in test shipping. See get_guides("floot-shipping"). Other enum values are beta-gated. Sending email needs no resource (@floot/email, get_guides("email")). The user's OWN key (their OpenAI key, an external database) goes through request_external_resource. Turning Floot Payments OFF (publishing is refused while it is attached with Stripe setup unfinished, also when the app no longer uses it): action "turn_off" with resource "payments". Owner only; ask the user first. It keeps the app's data and Stripe setup; the owner turns it back on in Floot (Services → Payments). Turning Floot Shipping OFF (publishing is refused while it is attached and Shippo is not connected, also when the app ships nothing): action "turn_off" with resource "shipping". Edit access; ask the user first. It keeps the app's data and Shippo connection; provisioning "shipping" again turns it back on.

  • app-connection — let this project's backend call functions ANOTHER Floot app exports (no API keys): pass app_target and app_functions. Only apps the user can edit, only functions in the other app's helpers/flootAppExports.tsx (saved is enough: write both apps first, connect, then publish both); the user confirms in a dialog. Read get_guides("app-calls") first.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectId": "<projectId>",
      "resource": "<resource>"
    },
    "name": "provision_resource"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNoDefault "provision". "turn_off" only with resource "payments" (turns Floot Payments off, owner only) or "shipping" (turns Floot Shipping off, edit access); only after the user confirms.
app_noteNoOnly for resource "app-connection": one sentence for the user on why this project needs these functions. Shown in the confirmation dialog.
resourceYes
projectIdYes
app_targetNoOnly for resource "app-connection": the OTHER Floot app — its project id, name.floot.app address or custom domain.
app_functionsNoOnly for resource "app-connection": the exact function names this project needs from the other app's helpers/flootAppExports.tsx.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / action / description
      Previous value: -"Default \"provision\". \"turn_off\" only with resource \"payments\": turns Floot Payments off for the project (owner only, after the user confirms)."New value: +"Default \"provision\". \"turn_off\" only with resource \"payments\" (turns Floot Payments off, owner only) or \"shipping\" (turns Floot Shipping off, edit access); only after the user confirms."
  2. Changed1 schema field changed
    • addedInput schema / properties / action
      Added value: +{
      +  "description": "Default \"provision\". \"turn_off\" only with resource \"payments\": turns Floot Payments off for the project (owner only, after the user confirms).",
      +  "enum": [
      +    "provision",
      +    "turn_off"
      +  ],
      +  "type": "string"
      +}
  3. Changed4 schema fields changed
    • addedInput schema / properties / app_functions
      Added value: +{
      +  "description": "Only for resource \"app-connection\": the exact function names this project needs from the other app's helpers/flootAppExports.tsx.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / app_note
      Added value: +{
      +  "description": "Only for resource \"app-connection\": one sentence for the user on why this project needs these functions. Shown in the confirmation dialog.",
      +  "type": "string"
      +}
    • addedInput schema / properties / app_target
      Added value: +{
      +  "description": "Only for resource \"app-connection\": the OTHER Floot app — its project id, name.floot.app address or custom domain.",
      +  "type": "string"
      +}
    • changedInput schema / properties / resource / enum
      Previous value: -[
      -  "database",
      -  "auth",
      -  "oauth-login",
      -  "microsoft-login",
      -  "google-integration",
      -  "microsoft-integration",
      -  "push-notifications",
      -  "self-edit",
      -  "payments",
      -  "shipping"
      -]New value: +[
      +  "database",
      +  "auth",
      +  "oauth-login",
      +  "microsoft-login",
      +  "google-integration",
      +  "microsoft-integration",
      +  "push-notifications",
      +  "self-edit",
      +  "payments",
      +  "shipping",
      +  "app-connection"
      +]
  4. Changed1 schema field changed
    • changedInput schema / properties / resource / enum
      Previous value: -[
      -  "database",
      -  "auth",
      -  "oauth-login",
      -  "microsoft-login",
      -  "google-integration",
      -  "microsoft-integration",
      -  "push-notifications",
      -  "self-edit",
      -  "payments"
      -]New value: +[
      +  "database",
      +  "auth",
      +  "oauth-login",
      +  "microsoft-login",
      +  "google-integration",
      +  "microsoft-integration",
      +  "push-notifications",
      +  "self-edit",
      +  "payments",
      +  "shipping"
      +]
  5. Changed1 schema field changed
    • changedInput schema / properties / resource / enum
      Previous value: -[
      -  "database",
      -  "auth",
      -  "oauth-login",
      -  "microsoft-login",
      -  "google-integration",
      -  "microsoft-integration",
      -  "push-notifications",
      -  "self-edit"
      -]New value: +[
      +  "database",
      +  "auth",
      +  "oauth-login",
      +  "microsoft-login",
      +  "google-integration",
      +  "microsoft-integration",
      +  "push-notifications",
      +  "self-edit",
      +  "payments"
      +]
  6. Changed1 schema field changed
    • changedInput schema / properties / resource / enum
      Previous value: -[
      -  "database",
      -  "auth",
      -  "oauth-login",
      -  "microsoft-login",
      -  "google-integration",
      -  "microsoft-integration",
      -  "push-notifications"
      -]New value: +[
      +  "database",
      +  "auth",
      +  "oauth-login",
      +  "microsoft-login",
      +  "google-integration",
      +  "microsoft-integration",
      +  "push-notifications",
      +  "self-edit"
      +]
  7. First observed

TDQS

A4.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations, it discloses idempotency, server-side secret minting, seed-file skipping, publish-refusal conditions for attached payments/shipping, owner/edit access differences, and the user confirmation dialog for app-connection. These are exactly the behavioral traits an agent needs before invoking a mutating tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but front-loaded with the core purpose, followed by a resource-by-resource list where each bullet carries distinct operational meaning. Some turn_off and app-connection details are repeated across the description and schema, but the length is largely justified by the eleven-value enum.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex provisioning tool with six parameters, no output schema, and multiple side effects, the description covers resource behavior, prerequisites, confirmation requirements, and alternative tools. An agent has enough information to select the correct resource and understand the consequences of provisioning or turning off payments/shipping.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%, and the description substantially compensates by explaining each resource enum value and the special app-connection parameters app_target, app_functions, and app_note. It adds some repetition of the action parameter's turn_off behavior already captured in the schema description, but the overall semantic value is high.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description begins with a specific verb and resource: provisioning a Floot-managed backend resource, minting secrets server-side, and seeding working code. It then enumerates each supported resource with concrete effects such as setting FLOOT_DATABASE_URL or injecting auth pages, making it clearly distinguishable from siblings like request_external_resource.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly routes cases: the user's own key or external database goes through request_external_resource, email needs no resource, and app-connection requires reading get_guides("app-calls") first. It also states when to use turn_off versus provisioning and that the user should be asked before turning payments or shipping off.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources