Skip to main content
Glama
mongodb-js

MongoDB MCP Server

Official
by mongodb-js

atlas-list-orgs

Read-only

Retrieve and display all MongoDB Atlas organizations you have access to for managing cloud database resources.

Instructions

List MongoDB Atlas organizations

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The execute method implements the tool logic: calls the Atlas API to list organizations, handles empty results, maps to name/id, and formats output using formatUntrustedData.
        protected async execute(): Promise<CallToolResult> {
            const data = await this.session.apiClient.listOrgs();
    
            if (!data?.results?.length) {
                return {
                    content: [{ type: "text", text: "No organizations found in your MongoDB Atlas account." }],
                };
            }
    
            const orgs = data.results.map((org) => ({
                name: org.name,
                id: org.id,
            }));
    
            return {
                content: formatUntrustedData(
                    `Found ${data.results.length} organizations in your MongoDB Atlas account.`,
                    JSON.stringify(orgs)
                ),
            };
        }
    }
  • The tool class definition and name property registration for 'atlas-list-orgs'. Extends AtlasToolBase which likely handles MCP tool protocol.
    export class ListOrganizationsTool extends AtlasToolBase {
        public name = "atlas-list-orgs";
  • Empty input schema indicating no arguments required for this tool.
    protected argsShape = {};
  • Barrel export re-exposing the tool for easy import in registration contexts.
    export { ListOrganizationsTool } from "./read/listOrgs.js";
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows this is a safe read operation. The description adds no behavioral context beyond the basic purpose—no information about permissions needed, rate limits, pagination, or what 'organizations' entails in MongoDB Atlas. With annotations covering safety, this is adequate but minimal.

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 a single, efficient sentence with no wasted words. It's front-loaded with the core action and resource, making it easy to scan and understand quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter read tool with annotations covering safety, the description is minimally complete. However, without an output schema, it doesn't explain what 'organizations' includes (e.g., IDs, names, metadata), and given the complexity of MongoDB Atlas, more context on scope or typical use could be helpful. It's adequate but leaves gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, and schema description coverage is 100% (though trivial). The description doesn't need to explain parameters, so it meets expectations. A baseline of 4 is appropriate as it avoids misleading or redundant parameter information.

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 action ('List') and resource ('MongoDB Atlas organizations'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'atlas-list-clusters' or 'atlas-list-projects' beyond the resource type, which prevents a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. With multiple 'atlas-list-*' siblings available, there's no indication of whether this is for administrative overview, project selection, or other contexts, leaving usage decisions ambiguous.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mongodb-js/mongodb-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server