Skip to main content
Glama

edubase_get_integration_keys

Read-onlyIdempotent

Retrieve API, LTI 1.0/1.1, or LTI 1.3 integration keys and secrets so you can configure and authenticate the connection securely. Keep returned credentials confidential.

Instructions

Get the keys and secrets of an integration: the app and secret of API integrations, the consumer key and secret (LTI 1.0/1.1) or the JWK set URL and public key (LTI 1.3) of LMS integrations. Treat the secrets as confidential.

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_get_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

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false), so the description's main added value is the explicit confidentiality warning, which meaningfully shapes how an agent should handle and surface the output. It does not, however, say whether the secrets are always retrievable or only for certain integration states, nor mention authorization requirements beyond the secrecy note.

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?

Two sentences, front-loaded with the core action, followed by the payload breakdown and a one-line handling caveat. No filler and nothing buried.

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?

An output schema exists, so return-value shape need not be explained, and the description still helpfully names the key fields per integration type. What remains thin is error/edge behavior for an unknown or non-existent integration, which an agent calling a single-required-param read tool might otherwise have to discover by trial.

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 coverage is 100% and the single parameter 'integration' is documented as an 'integration identification string', so the schema carries the load. The description adds some useful domain framing by naming the integration varieties (API vs LMS, LTI 1.0/1.1 vs 1.3), but it never states the expected identifier format or where to obtain one.

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?

States a specific verb and resource ('Get the keys and secrets of an integration') and then enumerates exactly which credentials are returned for each integration kind (API app/secret, LTI 1.0/1.1 consumer key/secret, LTI 1.3 JWK set URL/public key). That enumeration clearly separates it from edubase_get_integration, which by contrast can only return general integration metadata.

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?

Usage is only implied: wanting credentials for a known integration. Nothing tells the agent when to prefer this over get_integration or when to use edubase_post_integration_keys (e.g. rotation/regeneration), and no prerequisites or failure conditions are mentioned.

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