Skip to main content
Glama

get-specific-board-member

Retrieve details of a specific member on a Miro board by providing board and member IDs to access individual contributor information.

Instructions

Retrieve details of a specific member on a Miro board

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boardIdYesID of the board
memberIdYesID of the specific board member to retrieve

Implementation Reference

  • The handler function that implements the core logic of the 'get-specific-board-member' tool. It validates inputs, calls the MiroClient API to fetch the specific board member, and returns the result as JSON or an error response.
    fn: async ({ boardId, memberId }) => {
      try {
        if (!boardId) {
          return ServerResponse.error("Board ID is required");
        }
    
        if (!memberId) {
          return ServerResponse.error("Member ID is required");
        }
    
        const result = await MiroClient.getApi().getSpecificBoardMember(boardId, memberId);
    
        return ServerResponse.text(JSON.stringify(result, null, 2));
      } catch (error) {
        process.stderr.write(`Error retrieving specific board member: ${error}\n`);
        return ServerResponse.error(error);
      }
    }
  • The schema definition for the tool, including name, description, and Zod-validated input parameters (boardId and memberId).
    const getSpecificBoardMemberTool: ToolSchema = {
      name: "get-specific-board-member",
      description: "Retrieve details of a specific member on a Miro board",
      args: {
        boardId: z.string().describe("ID of the board"),
        memberId: z.string().describe("ID of the specific board member to retrieve")
      },
  • src/index.ts:174-174 (registration)
    The line where the get-specific-board-member tool is registered with the ToolBootstrapper.
    .register(getSpecificBoardMemberTool)
Behavior2/5

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

With no annotations provided, the description carries full burden but only states it 'retrieves details' without disclosing behavioral traits like authentication needs, rate limits, error conditions, or what details are returned. This is inadequate for a read operation with zero annotation coverage.

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 appropriately sized for a simple retrieval tool and front-loads the core 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?

For a simple read operation with 2 parameters and 100% schema coverage, the description is minimally adequate. However, with no annotations and no output schema, it should ideally provide more context about return values or behavioral constraints to reach higher completeness.

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%, so the schema fully documents both parameters. The description adds no additional meaning beyond what's in the schema (e.g., format of IDs, where to find them), meeting the baseline for high schema coverage.

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 verb ('Retrieve details') and resource ('specific member on a Miro board'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling 'get-all-board-members' or 'get-organization-member', which would require a 5.

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 versus alternatives like 'get-all-board-members' or 'get-organization-member'. The description only states what it does, not when it's appropriate.

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