Skip to main content
Glama

edubase_patch_integration

Idempotent

Enable or disable an integration, move it to another organization, or set its secret lifetime to control access and lifecycle.

Instructions

Enable or disable an integration, move it to another organization or set its secret lifetime.

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": {
      "integration": "<integration>"
    },
    "name": "edubase_patch_integration"
  }
}

Input Schema

NameRequiredDescriptionDefault
activeNoenable or disable the integration
integrationYesintegration identification string
organizationNoorganization identification string to move the integration to, only an organization of the API application owner can be used, only the owner of the integration (or an administrator) can change the organization, send "none" (or an empty value) to remove the integration from its current organization, always the organization of the user for organizational members
secret_lifetimeNooptional secret lifetime in days, 0 for never, as in edubase_post_integration

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.16
    • addedInput schema / properties / secret_lifetime
      Added value: +{
      +  "description": "optional secret lifetime in days, 0 for never, as in edubase_post_integration",
      +  "maximum": 9999,
      +  "minimum": 0,
      +  "type": "integer"
      +}
  2. Changed1 schema field changedv1.2.15
    • addedInput schema / properties / organization
      Added value: +{
      +  "description": "organization identification string to move the integration to, only an organization of the API application owner can be used, only the owner of the integration (or an administrator) can change the organization, send \"none\" (or an empty value) to remove the integration from its current organization, always the organization of the user for organizational members",
      +  "type": "string"
      +}
  3. Addedv1.2.9
  4. Removedv1.2.8
  5. Changed1 schema field changedv1.1.2
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
  6. First observedv1.0.22

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety and idempotency profile is covered. The description adds the mutation scope by naming the three modifiable aspects, but it does not disclose partial-update semantics, permission requirements, or response behavior beyond what the schema says.

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 a single front-loaded sentence that efficiently enumerates the tool's capabilities with no filler. It could be slightly clearer with a stronger separation between the alternative operations, but it is appropriately sized.

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?

The definition is adequate for a four-parameter patch tool because the schema fully documents parameters and annotations cover safety and idempotency. However, with no output schema, the description does not explain the response, error behavior, or whether omitted fields remain unchanged, leaving meaningful behavioral context unstated.

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 the input schema already documents active, integration, organization, and secret_lifetime in detail. The description maps its three operations to those parameters at a high level but adds little meaning beyond the schema, so the baseline of 3 is appropriate.

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 states a specific mutation resource and enumerates the three patchable operations: enable/disable, move organization, and set secret lifetime. It is clear what the tool does, though it does not explicitly distinguish itself from sibling tools such as edubase_post_integration or edubase_delete_integration.

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

Usage Guidelines2/5

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

The description lists what can be changed but gives no explicit guidance on when to use this tool versus siblings, no prerequisites, and no exclusions. An agent can infer it is for modifying an existing integration, but the definition does not state that.

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