Skip to main content
Glama

get-board-classification

Retrieve board classification data for enterprise Miro boards to organize and manage content effectively.

Instructions

Retrieves board classification for a board (Enterprise only)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orgIdYesid of the organization
teamIdYesid of the team
boardIdYesUnique identifier of the board that you want to retrieve

Implementation Reference

  • The asynchronous function implementing the core logic of the 'get-board-classification' tool. It calls the Miro API to fetch board classification and returns the response or handles errors.
    fn: async ({ orgId, teamId, boardId }) => {
      try {
        const response = await MiroClient.getApi().enterpriseDataclassificationBoardGet(orgId, teamId, boardId);
    
        return ServerResponse.text(JSON.stringify(response.body, null, 2));
      } catch (error) {
        process.stderr.write(`Error retrieving board classification: ${error}\n`);
        return ServerResponse.error(error);
      }
    }
  • Zod schema defining the input arguments for the tool: orgId, teamId, and boardId.
    args: {
      orgId: z.string().describe("id of the organization"),
      teamId: z.string().describe("id of the team"),
      boardId: z.string().describe("Unique identifier of the board that you want to retrieve"),
    },
  • src/index.ts:190-190 (registration)
    Registers the getBoardClassificationTool with the ToolBootstrapper instance in the main server setup.
    .register(getBoardClassificationTool)
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 'Retrieves' (implying read-only) and 'Enterprise only' (a constraint), but lacks details on permissions needed, rate limits, error conditions, or what the classification data looks like. For a read operation with no annotation coverage, this is insufficient.

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 zero wasted words. It's front-loaded with the core purpose and includes a key constraint ('Enterprise only') concisely. Every part of the sentence serves a purpose.

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 moderate complexity (3 required parameters, no output schema, no annotations), the description is minimally adequate. It states the purpose and a constraint but lacks behavioral details, usage context, and output information. It's complete enough to understand what it does but not how to use it effectively.

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?

Schema description coverage is 100%, with all three parameters (orgId, teamId, boardId) clearly documented in the schema. The description adds no additional parameter information beyond what the schema provides, so it meets the baseline of 3 for adequate coverage without adding value.

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 ('Retrieves') and resource ('board classification for a board'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'get-specific-board' or 'get-board-export-job-status', which also retrieve board-related information but for different data types.

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. It mentions 'Enterprise only', which is a constraint but not a usage guideline. There's no indication of prerequisites, when to choose this over other board-related get tools, or any exclusions.

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