Retrieve managed, non-generated users from EduBase. Use pagination and search to filter results for user management tasks.
List managed, non-generated users.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | page number (default: 1), not used in search mode! | |
| limit | No | limit number of results (default: 16) | |
| search | No | search string to filter results |
| Name | Required | Description | Default |
|---|---|---|---|
| users | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v1.1.2Input schema / $schemaAdded value: +"http://json-schema.org/draft-07/schema#"Input schema / properties / limit / maximumAdded value: +9007199254740991Input schema / properties / limit / minimumAdded value: +-9007199254740991Input schema / properties / limit / typePrevious value: -"number"New value: +"integer"Input schema / properties / page / maximumAdded value: +9007199254740991Input schema / properties / page / minimumAdded value: +-9007199254740991Input schema / properties / page / typePrevious value: -"number"New value: +"integer"Input schema / requiredRemoved value: -[]Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": false,
+ "properties": {
+ "users": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "name": {
+ "description": "full name of the user",
+ "type": "string"
+ },
+ "user": {
+ "description": "user identification string",
+ "type": "string"
+ }
+ },
+ "required": [
+ "user",
+ "name"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "users"
+ ],
+ "type": "object"
+}v1.0.22Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate read-only behavior. Description adds the 'non-generated' filter, but lacks disclosure of pagination behavior or that search mode disables page parameter (though schema covers this). Minimal added value beyond annotations.
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?
Description is a single, front-loaded sentence that efficiently conveys the core purpose. No unnecessary words.
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?
While an output schema exists (reducing burden), the description omits clarifying what 'managed, non-generated' means or how this tool relates to other user listing tools. Adequate but could be more 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 coverage is 100% with clear descriptions for all three parameters. Description does not add additional meaning beyond what the schema already provides, so baseline score of 3 is appropriate.
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?
Description clearly states the tool lists users with qualifiers 'managed, non-generated'. However, it does not distinguish from sibling tools like edubase_get_user (single user) or edubase_get_user_search, which could cause confusion.
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 on when to use this tool versus alternatives. No prerequisites or exclusions mentioned, leaving the agent to infer context from sibling names.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/EduBase/MCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server