Skip to main content
Glama

get-organization-info

Retrieve organization details from Miro for Enterprise accounts by providing the organization ID.

Instructions

Retrieves organization information (Enterprise only)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orgIdYesid of the organization

Implementation Reference

  • The handler function that executes the tool logic: calls the Miro API to get organization info by orgId and returns JSON response or error.
    fn: async ({ orgId }) => {
      try {
        const response = await MiroClient.getApi().enterpriseGetOrganization(orgId);
    
        return ServerResponse.text(JSON.stringify(response.body, null, 2));
      } catch (error) {
        process.stderr.write(`Error retrieving organization info: ${error}\n`);
        return ServerResponse.error(error);
      }
    }
  • Tool schema defining name, description, and input parameters with Zod validation for orgId.
    const getOrganizationInfoTool: ToolSchema = {
      name: "get-organization-info",
      description: "Retrieves organization information (Enterprise only)",
      args: {
        orgId: z.string().describe("id of the organization")
      },
  • src/index.ts:196-196 (registration)
    Registration of the tool in the ToolBootstrapper chain.
    .register(getOrganizationInfoTool)
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves information, implying a read-only operation, but doesn't cover critical aspects like authentication requirements, rate limits, error handling, or what the return data includes. For a tool with no annotations, this leaves significant gaps in understanding its behavior.

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

Conciseness4/5

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

The description is very concise with just one sentence, making it easy to parse quickly. However, it could be more front-loaded by explicitly stating the tool's name or key action first, and the parenthetical '(Enterprise only)' might be better integrated for clarity. Overall, it's efficient with minimal waste.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is insufficient for a tool that retrieves organizational data. It doesn't explain what information is returned (e.g., details like name, settings, or metadata), how to interpret the 'Enterprise only' restriction, or potential errors. For a read operation with no structured output guidance, more context is needed to ensure proper usage.

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 input schema has 100% description coverage, with the single parameter 'orgId' clearly documented as 'id of the organization'. The description doesn't add any extra meaning beyond this, such as format examples or sourcing details, but since the schema is comprehensive, the baseline score of 3 is appropriate as it adequately covers the parameter semantics.

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's purpose with a specific verb ('Retrieves') and resource ('organization information'), making it easy to understand what it does. However, it doesn't differentiate from sibling tools like 'get-organization-member' or 'get-organization-members', which also retrieve organization-related data, leaving some ambiguity about scope.

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 minimal guidance with the note '(Enterprise only)', implying usage is restricted to Enterprise contexts, but it doesn't explain when to use this tool versus alternatives like 'get-organization-member' or 'get-organization-members'. No explicit when/when-not scenarios or prerequisites are mentioned, leading to potential confusion.

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/k-jarzyna/mcp-miro'

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