Skip to main content
Glama
EduBase

EduBase MCP Server

Official
by EduBase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

edubase_get_tag

Read-onlyIdempotent

Retrieve a tag's title, external identifier, color, and icon from EduBase to identify and manage educational content.

Instructions

Get the details of a tag: title, external identifier, color and icon.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagYestag identification string

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
tagYes
iconYes
colorYes
titleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.0.0
    • removedOutput schema / properties / color / description
      Removed value: -"color in HEX format"
    • removedOutput schema / properties / icon / description
      Removed value: -"Font Awesome icon class name"
    • removedOutput schema / properties / id / description
      Removed value: -"external unique tag identifier (if set for the tag)"
    • removedOutput schema / properties / tag / description
      Removed value: -"tag identification string"
    • removedOutput schema / properties / title / description
      Removed value: -"title of the tag"
  2. Changed3 schema fields changedv1.2.15
    • removedOutput schema / properties / name
      Removed value: -{
-  "description": "title of the tag",
-  "type": "string"
-}
    • addedOutput schema / properties / title
      Added value: +{
+  "description": "title of the tag",
+  "type": "string"
+}
    • changedOutput schema / required
      Previous value: -[
-  "tag",
-  "name",
-  "color",
-  "icon"
-]New value: +[
+  "tag",
+  "title",
+  "color",
+  "icon"
+]
  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": {
+    "color": {
+      "description": "color in HEX format",
+      "type": "string"
+    },
+    "icon": {
+      "description": "Font Awesome icon class name",
+      "type": "string"
+    },
+    "id": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "external unique tag identifier (if set for the tag)"
+    },
+    "name": {
+      "description": "title of the tag",
+      "type": "string"
+    },
+    "tag": {
+      "description": "tag identification string",
+      "type": "string"
+    }
+  },
+  "required": [
+    "tag",
+    "name",
+    "color",
+    "icon"
+  ],
+  "type": "object"
+}
  6. First observedv1.0.22

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the core behavioral safety profile. The description adds the returned fields but does not disclose additional behavioral traits such as error behavior for an unknown tag or open-world lookup semantics. No contradiction with the 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 compact sentence that front-loads the action, names the target resource, and lists the relevant returned fields. There is no filler, repetition, or unnecessary detail.

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

Completeness5/5

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

For a single-parameter read-only lookup with a fully described parameter, strong safety annotations, and an output schema present, the description is sufficient for an agent to invoke the tool correctly. The lack of sibling-routing guidance is a usage-guidelines concern, not a completeness gap for this simple operation.

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 single 'tag' parameter is already documented as 'tag identification string'. The description adds no further parameter meaning, such as expected format or how to obtain the identifier, so the baseline of 3 is appropriate.

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 uses a specific verb ('Get') and a clear resource ('details of a tag'), and it enumerates the returned fields: title, external identifier, color and icon. It is clear enough to understand what the tool does, but it does not explicitly differentiate this from sibling tools like edubase_get_tags or edubase_get_content_tag.

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 intended use is implied: call this when you need details about a single identified tag. However, there is no explicit guidance about when to use this instead of edubase_get_tags (listing tags) or edubase_get_content_tag (content tags), leaving the most likely source of confusion unaddressed.

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