Skip to main content
Glama
EduBase

EduBase MCP Server

Official
by EduBase
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

edubase_post_integration_keys

Rotate integration keys or secrets for a specified integration by supplying its identifier, refreshing credentials for security.

Instructions

Rotate integration keys/secrets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
integrationYesintegration identification string

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
appNoAPI application identification string, only present if the integration is an API integration
jwkNoURL for the JWK (JSON Web Key) set, only present if the integration is an LMS integration using LTI 1.3
pemNoPEM formatted public key, only present if the integration is an LMS integration using LTI 1.3
secretNosecret key, only present if the integration is an API integration or an LMS integration using LTI 1.0/1.1
consumerNoconsumer key, only present if the integration is an LMS integration using LTI 1.0/1.1

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Addedv1.2.9
  2. Removedv1.2.8
  3. 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"
+}
  4. First observedv1.0.22

TDQS

B3.2/5.0
Behavior2/5

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

The description says 'Rotate' but does not disclose behavioral details such as whether old keys are invalidated, if the operation is reversible, required permissions, or rate limits. Annotations indicate destructiveHint=false and readOnlyHint=false, but the description does not clarify the actual impact of rotation (e.g., possible service disruption). This leaves significant ambiguity for an agent.

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

Conciseness5/5

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

The description consists of a single, concise sentence that immediately conveys the tool's action. There is no redundant or extraneous text—every word earns its place.

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

Completeness2/5

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

Despite having only one parameter and an output schema, the description omits crucial context: it doesn't confirm that the integration must already exist, what the output contains (though output schema exists), or any side effects. An agent cannot reliably use this tool without additional knowledge about rotation semantics.

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 input schema provides 100% coverage with a description for the single required parameter ('integration identification string'). The tool description adds no additional information about the parameter. Baseline for full coverage is 3, and the description neither adds nor detracts from the schema's clarity.

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 states 'Rotate integration keys/secrets,' which uses a specific verb ('Rotate') and clearly identifies the resource ('integration keys/secrets'). It distinguishes from sibling tools like edubase_get_integration_keys (retrieval) and edubase_post_integration (creation). This is a clear and unambiguous purpose.

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 provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites (e.g., existing integration) or scenarios where rotation is appropriate. With many sibling tools, such as edubase_get_integration_keys for viewing current keys, the lack of usage direction makes it hard for an agent to decide correctly.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/EduBase/MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server