Skip to main content
Glama

update_integration_models

DestructiveIdempotent

Bulk enable or disable integration models, register custom or fine-tuned models, set per-model hosts, headers, and static token pricing, and control whether future provider models start enabled.

Instructions

Bulk enable or disable integration models, register custom or fine-tuned models, set per-model hosts and headers, and attach static token pricing. allow_all_models controls whether future provider models start enabled. These changes affect every workspace using the integration; inspect list_integration_models first and use get_model_pricing when deriving custom rates. Returns success and the number of models updated.

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>",
      "models": "<models>"
    },
    "name": "update_integration_models"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe slug of the integration
modelsYesArray of model configurations to update
allow_all_modelsNoWhether newly available provider models are enabled by default

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. Changed5 schema fields changed
    • addedInput schema / properties / allow_all_models
      Added value: +{
      +  "description": "Whether newly available provider models are enabled by default",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / models / items / properties / base_model_slug
      Added value: +{
      +  "description": "Base model slug for a fine-tuned model",
      +  "type": "string"
      +}
    • addedInput schema / properties / models / items / properties / configurations
      Added value: +{
      +  "description": "Per-model custom upstream host and headers",
      +  "properties": {
      +    "custom_headers": {
      +      "additionalProperties": {
      +        "type": "string"
      +      },
      +      "description": "Headers sent only for this model; values may contain secrets",
      +      "propertyNames": {
      +        "type": "string"
      +      },
      +      "type": "object"
      +    },
      +    "custom_host": {
      +      "description": "Custom upstream URL used only for this model",
      +      "format": "uri",
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedInput schema / properties / models / items / properties / is_finetune
      Added value: +{
      +  "description": "Whether this entry is a fine-tuned model",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / models / items / properties / pricing_config
      Added value: +{
      +  "description": "Static custom pricing for this integration model",
      +  "properties": {
      +    "pay_as_you_go": {
      +      "description": "Pay-as-you-go rates for this integration model",
      +      "properties": {
      +        "request_token": {
      +          "description": "Input token pricing",
      +          "properties": {
      +            "price": {
      +              "description": "Static price per token in the integration pricing unit",
      +              "minimum": 0,
      +              "type": "number"
      +            }
      +          },
      +          "required": [
      +            "price"
      +          ],
      +          "type": "object"
      +        },
      +        "response_token": {
      +          "description": "Output token pricing",
      +          "properties": {
      +            "price": {
      +              "description": "Static price per token in the integration pricing unit",
      +              "minimum": 0,
      +              "type": "number"
      +            }
      +          },
      +          "required": [
      +            "price"
      +          ],
      +          "type": "object"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "type": {
      +      "const": "static",
      +      "description": "Static per-token pricing configuration",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "type"
      +  ],
      +  "type": "object"
      +}
  4. Addedv1.0.1
  5. Removed
  6. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, and the description corroborates with the blast-radius warning that changes 'affect every workspace using the integration.' It also clarifies allow_all_models affects future provider models, which the annotations cannot convey. Beyond that it adds little behavioral detail such as permission requirements or what happens to omitted models, so with annotations covering the safety profile a 3 is appropriate, though the workspace-wide warning is genuinely valuable.

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

Conciseness3/5

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

Three sentences, front-loaded with the capabilities, which is good structure. The final sentence about returning success and a count is low value because an output schema already exists, costing conciseness without adding information.

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

Completeness3/5

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

Given the output schema exists, the description needn't explain return values and in fact duplicates them. It covers scope and prerequisites well but omits what happens to models not listed, whether disabling is reversible, and any permission/auth requirements for a destructive workspace-wide mutation.

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%, so all three top-level parameters and the nested model objects are already documented. The description's note on allow_all_models ('whether future provider models start enabled') largely restates the schema's own wording, so the baseline 3 applies.

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 opens with specific verb+resource pairs: bulk enable/disable integration models, register custom or fine-tuned models, set per-model hosts and headers, and attach static pricing. This covers all four capabilities an agent would need to distinguish from siblings like delete_integration_model or list_integration_models.

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 gives explicit prerequisites and alternatives: 'inspect list_integration_models first' and 'use get_model_pricing when deriving custom rates.' Each alternative is tied to a condition, so the agent knows when to route elsewhere rather than inferring it.

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