Retrieve the external unique question ID from a question identification string. Simplifies mapping questions to their identifiers for quiz and exam management.
Get external unique question identifier by question identification string.
| Name | Required | Description | Default |
|---|---|---|---|
| question | Yes | question identification string |
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | ||
| question | Yes |
Changes observed during successful MCP inspections.
v2.0.0Output schema / properties / id / descriptionRemoved value: -"external unique question identifier (if set for the question)"Output schema / properties / question / descriptionRemoved value: -"question identification string"v1.1.2Input schema / $schemaAdded value: +"http://json-schema.org/draft-07/schema#"Output 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"
+ }
+ },
+ "required": [
+ "question"
+ ],
+ "type": "object"
+}v1.0.22Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds a small amount of context about resolving an identifier, but it does not disclose behavior such as failure modes, uniqueness guarantees, or what happens when no identifier is found.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, compact sentence with no extraneous words. It front-loads the verb and target resource, though the wording 'by question identification string' is slightly awkward.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter read-only tool with full schema coverage and an output schema, the description is minimally sufficient. However, it lacks any context about when this identifier lookup is appropriate or how it relates to the many question-related sibling tools, so it is not fully complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and the parameter description 'question identification string' already defines the single parameter. The tool description simply repeats this phrasing without adding format, example, or boundary information, so it adds little beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific action ('Get external unique question identifier') and the input basis ('question identification string'). It is clear enough to distinguish this from edubase_get_question and edubase_get_questions, though it does not explicitly contrast itself with them.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided about when to use this tool versus alternatives such as edubase_get_question, edubase_get_questions, or edubase_post_question_id. The description only states what the tool does, leaving the agent to infer appropriate usage from the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.