Skip to main content
Glama
EduBase

EduBase MCP Server

Official
by EduBase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

edubase_patch_organization

Idempotent

Update organization details by changing its title or custom fields. Use this tool to modify existing organizational information in EduBase.

Instructions

Update the title or custom fields of an organization.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNotitle of the organization
customNocustom field data, keyed by field name (sent as `custom_{field}`), only if the specified field is configured for the target EduBase instance
organizationYesorganization identification string

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.2.15
    • addedInput schema / properties / custom
      Added value: +{
+  "additionalProperties": {
+    "type": "string"
+  },
+  "description": "custom field data, keyed by field name (sent as `custom_{field}`), only if the specified field is configured for the target EduBase instance",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}
    • addedInput schema / properties / title
      Added value: +{
+  "description": "title of the organization",
+  "maxLength": 255,
+  "minLength": 1,
+  "type": "string"
+}
  2. Changed1 schema field changedv1.1.2
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
  3. First observedv1.0.22

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already signal non-read-only, idempotent, non-destructive behavior, so the bar is lower. The description adds only the scope of the update but does not disclose PATCH semantics such as whether omitted fields are left unchanged or whether the custom object is merged or replaced. No contradiction with annotations.

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 is a single front-loaded sentence with no filler. Every word adds information about the tool's effect, making it optimal for quick scanning.

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?

The schema and annotations carry much of the load, but the description alone leaves gaps: it does not state that at least one of title/custom should be provided, does not explain whether custom fields are merged or replaced, and omits the organization parameter requirement. For a PATCH operation with nested objects, this is a clear but incomplete picture.

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%, with each parameter already explained (title, custom keyed by field name, organization identifier). The description echoes 'title or custom fields' without adding syntax, constraints, or merge semantics beyond the schema, so the baseline of 3 applies.

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 names a specific verb ('Update'), a clear resource ('organization'), and the exact fields affected ('title or custom fields'), which also differentiates it from sibling tools like edubase_patch_organization_department. An agent can immediately identify what this tool changes.

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?

The description implies when to use the tool (for updating an organization's title or custom fields) but provides no explicit alternatives, exclusions, or prerequisites such as requiring the organization identifier. Unlike a tool that names a sibling or gives when-not-to-use conditions, this leaves routing decisions to inference.

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