EduBase MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

edubase_get_user_name

Read-onlyIdempotent

Fetch first, last, full, and display names for a user on EduBase using their user identification string. Get complete name details for personalized communication and accurate reporting.

Instructions

Get the first, last, full and display name of a user.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`user`	Yes	user identification string

Output Schema

TableJSON Schema

Name	Required	Description	Default
`user`	Yes
`full_name`	Yes
`last_name`	Yes
`first_name`	Yes
`display_name`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv2.0.0Sep 15, 2026
- removedOutput schema / properties / display_name / description
```
Removed value: -"display name"
```
- removedOutput schema / properties / first_name / description
```
Removed value: -"first name"
```
- removedOutput schema / properties / full_name / description
```
Removed value: -"full name"
```
- removedOutput schema / properties / last_name / description
```
Removed value: -"last name"
```
- removedOutput schema / properties / user / description
```
Removed value: -"the user identification string"
```

Changed2 schema fields changedv1.1.2Mar 13, 2026

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": {
+    "display_name": {
+      "description": "display name",
+      "type": "string"
+    },
+    "first_name": {
+      "description": "first name",
+      "type": "string"
+    },
+    "full_name": {
+      "description": "full name",
+      "type": "string"
+    },
+    "last_name": {
+      "description": "last name",
+      "type": "string"
+    },
+    "user": {
+      "description": "the user identification string",
+      "type": "string"
+    }
+  },
+  "required": [
+    "user",
+    "first_name",
+    "last_name",
+    "full_name",
+    "display_name"
+  ],
+  "type": "object"
+}

First observedv1.0.22Feb 21, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the agent knows this is a safe, repeatable read operation. The description is consistent with those annotations but adds no additional behavioral context such as what happens for missing or invalid users.

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 one short, front-loaded sentence with no filler. It directly states the returned name fields and wastes no words.

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 read-only lookup with strong annotation coverage and an output schema, the description is largely sufficient. The only notable gap is the lack of routing guidance among the many sibling user-related tools, but the description still allows correct invocation.

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?

The single 'user' parameter has a schema description ('user identification string'), giving 100% schema description coverage. The tool description does not add further meaning, 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.

Purpose4/5

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

The description clearly states a specific action ('Get') and resource ('first, last, full and display name of a user'), making the purpose easy to understand. It does not explicitly differentiate this from sibling tools such as edubase_get_user or edubase_post_user_name, so it loses the top score.

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 that the tool should be used when a user's name fields are needed, but it offers no explicit when-to-use instructions and does not mention alternatives like edubase_get_user, edubase_get_user_me, or edubase_get_user_search. Guidance is therefore only implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server