Skip to main content
Glama
EduBase

EduBase MCP Server

Official
by EduBase
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

edubase_patch_integration

Idempotent

Update an existing integration by enabling or disabling it, or moving it to a different organization. Specify the integration identifier and optional new organization.

Instructions

Update integration.

Input Schema

TableJSON 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

Schema Changelog

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

  1. 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"
+}
  2. Addedv1.2.9
  3. Removedv1.2.8
  4. Changed1 schema field changedv1.1.2
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
  5. First observedv1.0.22

TDQS

C2.4/5.0
Behavior2/5

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

The description adds no behavioral context beyond the operation name. It does not mention side effects, authorization requirements, or how the update interacts with organization ownership or external systems. Annotations indicate idempotent and non-destructive behavior, but the description itself contributes nothing.

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

Conciseness2/5

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

'Update integration.' is a single under-specified sentence that simply restates the tool name/title. It is concise but not usefully informative, and it fails to earn its place by adding any operational clarity.

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?

Given the absence of an output schema and the presence of nuanced behavior around organization ownership and 'none' removal semantics, the description is far too terse. The schema explains some parameter details, but the description provides no broader context about when or how the integration update should be used.

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 fully documents each parameter. The description adds no parameter-level meaning, but the schema carries the burden, so the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Update integration' clearly identifies the verb and resource, but it is extremely vague about what updating an integration entails. It does not distinguish itself from siblings like edubase_get_integration, edubase_post_integration, or edubase_delete_integration, nor does it mention what fields or behaviors are involved.

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 usage guidance is provided. The description does not state when to use this tool instead of creation, deletion, or retrieval tools, nor does it mention any prerequisites or alternative tools.

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