List organizations you own or manage. Supports pagination and search to filter the results.
List owned and managed organizations.
| 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 |
|---|---|---|---|
| organizations | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v1.2.15Output schema / properties / organizations / items / properties / nameRemoved value: -{
- "description": "title of the organization",
- "type": "string"
-}Output schema / properties / organizations / items / properties / titleAdded value: +{
+ "description": "title of the organization",
+ "type": "string"
+}Output schema / properties / organizations / items / requiredPrevious value: -[
- "organization",
- "name"
-]New value: +[
+ "organization",
+ "title"
+]v1.2.9v1.2.8v1.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": {
+ "organizations": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "id": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "description": "external unique organization identifier (if set for the organization)"
+ },
+ "name": {
+ "description": "title of the organization",
+ "type": "string"
+ },
+ "organization": {
+ "description": "organization identification string",
+ "type": "string"
+ }
+ },
+ "required": [
+ "organization",
+ "name"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "organizations"
+ ],
+ "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, covering the safety profile. The description adds no behavioral detail beyond what annotations provide, but it does not contradict them; the operation is a simple list, so no extra disclosure is critical.
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, concise sentence with no wasted words. It is appropriately sized for a simple read-only list operation and front-loads the core verb and resource.
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 straightforward list tool with rich annotations, a complete input schema, and an output schema present, the one-line description is nearly sufficient. However, it lacks differentiation from related sibling tools, which slightly reduces completeness in a large tool namespace.
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%, so all three parameters (page, limit, search) are already documented. The description adds no additional meaning or context for parameters, maintaining the baseline for high schema coverage.
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 specifies a clear verb 'List' and resource 'organizations', with scope 'owned and managed'. It distinguishes from singular 'edubase_get_organization' implicitly, though it does not explicitly name alternatives or clarify nuances like owned vs managed versus all accessible organizations.
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 siblings such as edubase_get_user_organizations or edubase_get_organization. The description provides no conditions, exclusions, or alternative routing, leaving the agent to infer applicability.
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