Skip to main content
Glama

update_integration_workspaces

DestructiveIdempotent

Control per-workspace and global integration access, cost/rate limits, usage resets, and default-provider creation; review current workspace settings first because changes apply immediately.

Instructions

Control per-workspace and global access to an integration, including cost/rate limits, usage resets, and automatic default-provider creation. global_workspace_access_enabled affects current and future workspaces; override_existing_workspace_access determines whether it replaces explicit workspace settings. Per-workspace default-provider fields override top-level values. Review list_integration_workspaces first because access and limits change downstream usage immediately.

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": {
      "slug": "<slug>",
      "workspaces": "<workspaces>"
    },
    "name": "update_integration_workspaces"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe slug of the integration
workspacesYesArray of workspace configurations to update
global_credit_limitNoGlobal cost credit limit applied with global workspace access
default_provider_slugNoDefault slug for providers auto-created in workspaces
global_rate_limit_rpmNoGlobal requests-per-minute limit for workspace access
global_alert_thresholdNoGlobal cost alert threshold applied to workspace access
create_default_providerNoAuto-create providers when granting workspace access
global_workspace_access_enabledNoEnable or disable access for all current and future workspaces
override_existing_workspace_accessNoApply global settings over existing per-workspace access

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. Changed10 schema fields changed
    • addedInput schema / properties / create_default_provider
      Added value: +{
      +  "description": "Auto-create providers when granting workspace access",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / default_provider_slug
      Added value: +{
      +  "description": "Default slug for providers auto-created in workspaces",
      +  "type": "string"
      +}
    • addedInput schema / properties / global_alert_threshold
      Added value: +{
      +  "description": "Global cost alert threshold applied to workspace access",
      +  "maximum": 100,
      +  "minimum": 0,
      +  "type": "number"
      +}
    • addedInput schema / properties / global_credit_limit
      Added value: +{
      +  "description": "Global cost credit limit applied with global workspace access",
      +  "exclusiveMinimum": 0,
      +  "type": "number"
      +}
    • addedInput schema / properties / global_rate_limit_rpm
      Added value: +{
      +  "description": "Global requests-per-minute limit for workspace access",
      +  "exclusiveMinimum": 0,
      +  "type": "number"
      +}
    • addedInput schema / properties / global_workspace_access_enabled
      Added value: +{
      +  "description": "Enable or disable access for all current and future workspaces",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / override_existing_workspace_access
      Added value: +{
      +  "description": "Apply global settings over existing per-workspace access",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / workspaces / items / properties / create_default_provider
      Added value: +{
      +  "description": "Override whether a provider is auto-created for this workspace",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / workspaces / items / properties / default_provider_slug
      Added value: +{
      +  "description": "Override the auto-created provider slug for this workspace",
      +  "type": "string"
      +}
    • addedInput schema / properties / workspaces / items / properties / reset_usage
      Added value: +{
      +  "description": "Reset exhausted usage status to active",
      +  "type": "boolean"
      +}
  4. Addedv1.0.1
  5. Removed
  6. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, so the safety profile is known; the description earns credit by explaining the blast radius beyond that — global_workspace_access_enabled altering current and future workspaces, and override_existing_workspace_access replacing explicit per-workspace settings. It stops short of saying whether replaced settings can be recovered.

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?

Four sentences, front-loaded with the scope statement, then the two precedence rules, then the prerequisite. Dense but every sentence carries distinct information; the phrasing around 'default-provider fields override top-level values' is compact rather than vague.

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?

For a destructive 9-parameter mutation with full schema coverage and an output schema, the description supplies what structured fields cannot: precedence rules and the prerequisite read. Return values need not be explained since an output schema exists, so the remaining gap is minor.

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 100%, so the baseline is 3, but the description adds genuine semantics the schema cannot express: the precedence between global and per-workspace default-provider fields, and the interaction between global_workspace_access_enabled and override_existing_workspace_access. That is precedence logic, not restated field text.

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?

The description names a specific verb ('Control') and a precise resource scope: per-workspace and global access to an integration, plus cost/rate limits, usage resets, and default-provider creation. That is clearly more than a restatement of the name, though it never differentiates itself from the near-identical sibling update_mcp_integration_workspaces.

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

Usage Guidelines4/5

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

It gives an explicit prerequisite: review list_integration_workspaces first, justified by 'access and limits change downstream usage immediately.' That is real ordering guidance. There is no when-not guidance or explicit statement of which sibling to pick for MCP integrations, so it stops short of a 5.

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