Skip to main content
Glama
EduBase

EduBase MCP Server

Official
by EduBase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

edubase_post_question_export

Read-only

Generate a download link to export a question as JSON. Reuses an existing valid link to avoid duplicates.

Instructions

Generate download link for exporting the question (in JSON format). If a previous valid link exists, it will be returned instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesexternal unique question identifier

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
urlYes
validYes
questionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.0.0
    • removedOutput schema / properties / id / description
      Removed value: -"external unique question identifier (if set for the question)"
    • removedOutput schema / properties / question / description
      Removed value: -"question identification string"
    • removedOutput schema / properties / url / description
      Removed value: -"download link for the question"
    • removedOutput schema / properties / valid / description
      Removed value: -"date of link expiration"
  2. 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": {
+    "id": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "external unique question identifier (if set for the question)"
+    },
+    "question": {
+      "description": "question identification string",
+      "type": "string"
+    },
+    "url": {
+      "description": "download link for the question",
+      "format": "uri",
+      "type": "string"
+    },
+    "valid": {
+      "description": "date of link expiration",
+      "type": "string"
+    }
+  },
+  "required": [
+    "question",
+    "url",
+    "valid"
+  ],
+  "type": "object"
+}
  3. First observedv1.0.22

TDQS

A3.8/5.0
Behavior4/5

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

The description adds meaningful behavioral context beyond the annotations: it discloses that if a previous valid link exists, it will be returned instead of generating a new one. This is a caching/reuse behavior that an agent would not know from the readOnlyHint=true annotation alone. The description also implies the operation is non-destructive and read-only, consistent 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?

Two sentences with no wasted words. The primary action is stated first, followed by the important caching behavior. Every word earns its place, and the description is appropriately sized for a single-parameter tool.

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?

For a simple single-parameter tool with a readOnlyHint and an output schema, the description is largely complete. It explains the core behavior and the caching nuance. It doesn't mention the format of the download link or any expiration details, but the output schema likely covers the return structure. The description is sufficient for an agent to invoke the tool correctly.

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 schema already documents the single 'id' parameter as an external unique question identifier. The description doesn't add additional meaning about the parameter beyond what the schema provides, but it does clarify the parameter's role in the export context. Baseline 3 is appropriate since the schema carries the semantic weight.

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 clearly states the tool's function: generating a download link for exporting a question in JSON format. It identifies the specific resource (question) and the action (generate download link). However, it doesn't explicitly differentiate from sibling tools like edubase_get_question or edubase_post_question_export, though the export-specific verb and format make it reasonably distinct.

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 this tool: when you need a download link for a question export. It doesn't explicitly state when not to use it or mention alternatives like edubase_get_question for retrieving question data directly. The context is clear enough for an agent to infer the primary use case, but lacks explicit routing guidance.

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