Skip to main content
Glama

edubase_post_integration_keys

Rotates an integration's keys and secrets, returns the new credentials, and invalidates the previous keys while restarting the secret lifetime. Confirm with the user before use.

Instructions

Rotate the keys and secrets of an integration and return the new ones, the previous keys stop working and the secret lifetime restarts. Confirm with the user 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": {
      "integration": "<integration>"
    },
    "name": "edubase_post_integration_keys"
  }
}

Input Schema

NameRequiredDescriptionDefault
integrationYesintegration identification string

Output Schema

NameRequiredDescriptionDefault
appNo
jwkNo
pemNo
secretNo
expiresNo
consumerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.16
    • addedOutput schema / properties / expires
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
  2. Changed5 schema fields changedv2.0.0
    • removedOutput schema / properties / app / description
      Removed value: -"API application identification string, only present if the integration is an API integration"
    • removedOutput schema / properties / consumer / description
      Removed value: -"consumer key, only present if the integration is an LMS integration using LTI 1.0/1.1"
    • removedOutput schema / properties / jwk / description
      Removed value: -"URL for the JWK (JSON Web Key) set, only present if the integration is an LMS integration using LTI 1.3"
    • removedOutput schema / properties / pem / description
      Removed value: -"PEM formatted public key, only present if the integration is an LMS integration using LTI 1.3"
    • removedOutput schema / properties / secret / description
      Removed value: -"secret key, only present if the integration is an API integration or an LMS integration using LTI 1.0/1.1"
  3. Addedv1.2.9
  4. Removedv1.2.8
  5. Changed2 schema fields changedv1.1.2
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "app": {
      +      "description": "API application identification string, only present if the integration is an API integration",
      +      "type": "string"
      +    },
      +    "consumer": {
      +      "description": "consumer key, only present if the integration is an LMS integration using LTI 1.0/1.1",
      +      "type": "string"
      +    },
      +    "jwk": {
      +      "description": "URL for the JWK (JSON Web Key) set, only present if the integration is an LMS integration using LTI 1.3",
      +      "type": "string"
      +    },
      +    "pem": {
      +      "description": "PEM formatted public key, only present if the integration is an LMS integration using LTI 1.3",
      +      "type": "string"
      +    },
      +    "secret": {
      +      "description": "secret key, only present if the integration is an API integration or an LMS integration using LTI 1.0/1.1",
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  6. First observedv1.0.22

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations, the description discloses the key consequences: new keys and secrets are returned, the previous keys stop working, and the secret lifetime restarts. The only tension is destructiveHint=false, which can reasonably be read as "the integration itself is not deleted" since the description warns of, rather than contradicts, that annotation.

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?

Two sentences, front-loaded with the action and ending with the safety instruction, with little waste. Minor redundancy between "rotate the keys and secrets" and "return the new ones" keeps it from a 5.

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 one-parameter mutation with an output schema and annotations already present, the description covers the essential effects and the confirmation requirement. Return-value shape need not be explained because an output schema exists.

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?

The schema describes the single required parameter "integration" at 100% coverage, so the description adds no format, ID-style, or lookup guidance beyond it. Baseline 3 applies when the schema carries the parameter burden.

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?

"Rotate the keys and secrets of an integration" is a specific verb + resource and clearly separates this from a read such as edubase_get_integration_keys by emphasizing that new values are produced. It does not name the read sibling explicitly, so an agent must infer the contrast rather than being routed.

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?

"Confirm with the user first" is a real precondition and the strongest usage signal here, but there is no statement of when rotation is appropriate versus merely inspecting keys with the sibling get tool, nor of prerequisites such as ownership scope. Usage is implied by the destructive effect rather than spelled out.

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