Skip to main content
Glama

getOrganizationAdmins

Retrieve a list of administrators for a Meraki organization.

Instructions

Get organization administrators

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationIdNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Synchronous MCP tool handler for get_organization_admins. Calls dashboard.organizations.getOrganizationAdmins() and returns JSON result.
    @mcp.tool()
    def get_organization_admins(org_id: str = None) -> str:
        """Get a list of organization admins"""
        organization_id = org_id or MERAKI_ORG_ID
        admins = dashboard.organizations.getOrganizationAdmins(organization_id)
        return json.dumps(admins, indent=2)
  • Async MCP tool handler for getOrganizationAdmins. Delegates to call_meraki_method('organizations', 'getOrganizationAdmins', ...) with optional organizationId parameter. This is the primary handler in the dynamic file.
    @mcp.tool()
    async def getOrganizationAdmins(organizationId: str = None) -> str:
        """Get organization administrators"""
        params = {}
        if organizationId:
            params['organizationId'] = organizationId
        return await call_meraki_method("organizations", "getOrganizationAdmins", **params)
  • meraki-mcp.py:610-610 (registration)
    Registered as MCP tool via @mcp.tool() decorator on get_organization_admins function (snake_case name).
    @mcp.tool()
  • Registered as MCP tool via @mcp.tool() decorator on getOrganizationAdmins function (camelCase name). Listed as one of 12 pre-registered tools.
    @mcp.tool()
  • call_meraki_method helper function that wraps _call_meraki_method_internal in async, used by the getOrganizationAdmins handler in meraki-mcp-dynamic.py.
    async def call_meraki_method(section: str, method: str, **params) -> str:
        """Internal async wrapper for pre-registered tools"""
        return await to_async(_call_meraki_method_internal)(section, method, params)
Behavior2/5

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

With no annotations, the description carries full burden. It only says 'Get', implying a read operation, but does not explicitly state read-only nature, permissions needed, or any side effects. The description is insufficient for behavioral transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence, but it is too minimal to fully convey the tool's purpose and usage. It prioritizes brevity over completeness.

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?

Given the tool's simplicity (one optional parameter, output schema present), the description is barely adequate. It covers the basic action but lacks parameter and usage context.

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

Parameters1/5

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

Schema description coverage is 0%. The description does not mention the single parameter 'organizationId', its role, or constraints. Parameter semantics are completely absent.

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 tool gets organization administrators. It uses a specific verb ('Get') and resource ('organization administrators'), distinguishing it from sibling tools like getOrganizationDevices or getOrganizationNetworks. However, it does not specify whether it returns a list or a single item.

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?

No guidance is provided on when to use this tool vs alternatives. There is no mention of required input, prerequisites, or comparative context with other tools.

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/CiscoDevNet/meraki-magic-mcp-community'

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