Skip to main content
Glama

create_provider

Create a workspace provider backed by an organization integration, with independent usage limits, rate limits, and expiration, and return its new ID and slug.

Instructions

Create a workspace provider backed by an org integration. The provider inherits the integration key, but its limits and expiration are enforced independently for that workspace. Returns the new provider id and slug.

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": {
      "name": "<name>",
      "integration_id": "<integration_id>"
    },
    "name": "create_provider"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesDisplay name for the provider
noteNoOptional note or description for the provider
slugNoCustom slug for the provider. Auto-generated with random suffix if omitted
expires_atNoExpiration date in ISO 8601 format
credit_limitNoCredit limit for usage
workspace_idNoWorkspace ID - required when using organization admin API keys
integration_idYesIntegration slug for the provider (e.g., 'openai', 'anthropic', 'azure-openai')
periodic_resetNoPeriod for resetting usage limits: 'monthly' or 'weekly'. Defaults to 'monthly'.
alert_thresholdNoAlert threshold percentage (0-100)
rate_limit_unitNoMust be provided together with rate_limit_value. Values: 'rpm' (requests/min), 'rph' (requests/hour), or 'rpd' (requests/day).
rate_limit_valueNoMust be provided together with rate_limit_unit.
usage_limit_typeNoType of usage limit: 'cost' (monetary) or 'tokens' (token count). Defaults to 'cost'.

Output Schema

NameRequiredDescriptionDefault
okYesCall succeeded
dataNoSuccess payload
errorNoFailure details

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.16.5
    • changedOutput schema / properties / data / description
      Previous value: -"Structured success payload when ok is true"New value: +"Success payload"
    • changedOutput schema / properties / error / description
      Previous value: -"Structured error payload when ok is false"New value: +"Failure details"
    • changedOutput schema / properties / error / properties / details / description
      Previous value: -"Optional structured error details"New value: +"Extra error details"
    • changedOutput schema / properties / error / properties / message / description
      Previous value: -"Human-readable error message"New value: +"Error message"
    • changedOutput schema / properties / ok / description
      Previous value: -"Whether the tool call succeeded and returned structured data"New value: +"Call succeeded"
  2. Changed2 schema fields changedv1.0.9
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. Addedv1.0.1
  4. Removed
  5. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive, open-world write, so the safety bar is partly covered. The description adds genuinely non-obvious behavior: the provider inherits the integration key but enforces limits and expiration independently per workspace. It omits failure/duplicate behavior, which for a non-idempotent create would have been valuable.

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?

Three tight sentences with the core purpose and the key inheritance/limit rule front-loaded. The closing sentence about returning the new id and slug is mildly redundant given an output schema exists, but it is short and not harmful.

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

Completeness4/5

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

With 12 parameters, full schema coverage, an output schema, and annotations, the description only needs to supply purpose and non-obvious semantics, which it does via the inheritance and independent-enforcement explanation. Gaps around the conditional workspace_id/org-admin-key case are covered in the schema, so nothing critical is missing.

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

Parameters3/5

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

Schema description coverage is 100%, including enum values and the rate_limit_unit/value pairing rule, so the schema carries the parameter burden. The description adds no parameter-level meaning beyond referencing the integration and independent enforcement, making the baseline of 3 correct.

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

Purpose4/5

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

States a specific verb and resource ('Create a workspace provider') and immediately qualifies it with 'backed by an org integration,' which separates it from plain integration creation. It does not explicitly contrast with update_provider or create_integration, so a sibling distinction is only implied.

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

Usage Guidelines3/5

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

Usage is implied: create a provider when you want workspace-scoped limits over a shared org integration. There is no explicit when-to-use/when-not guidance, no mention of prerequisites (the referenced integration must already exist), and no named alternative such as update_provider for modifying an existing one.

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

Deploy Server

Other Tools