Skip to main content
Glama
EduBase

EduBase MCP Server

Official
by EduBase
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

edubase_get_integration_keys

Read-onlyIdempotent

Retrieve integration keys and secrets for external services. Use this tool to obtain authentication credentials required for configuring EduBase integrations.

Instructions

Get 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

C2.9/5.0
Behavior2/5

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

The description adds no behavioral information beyond what the annotations already declare (readOnly, openWorld, idempotent, not destructive). It does not disclose that the tool returns sensitive secrets, any permission requirements, or how the keys are scoped to an integration. With annotations covering the core safety profile, the description's lack of additional context earns a low score.

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 with no wasted words. It is minimally concise, but could be slightly expanded to include more context (e.g., the nature of the returned keys) without becoming verbose.

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 tool has one parameter, an output schema, and comprehensive annotations, the description is minimally complete. It does not explain the purpose of integration keys, the format of the output, or how the 'integration' parameter is used. The output schema may cover the return structure, but the description lacks context for a user unfamiliar with the domain.

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% (the 'integration' parameter is described as 'integration identification string'). The tool description does not provide any additional meaning for the parameter. Baseline is 3 due to high coverage; no extra value added.

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 'Get integration keys/secrets' clearly states the action (get) and the resource (integration keys/secrets). It distinguishes itself from siblings like edubase_get_integration (which likely gets integration details) and edubase_post_integration_keys (which creates keys). However, it does not explicitly differentiate itself or elaborate on the relationship between 'integration keys' and the 'integration' parameter.

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?

No guidance is provided on when to use this tool versus alternatives such as edubase_get_integration or edubase_post_integration_keys. There is no mention of prerequisites, context, or exclusions, leaving the agent to infer usage from the tool name alone.

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