Skip to main content
Glama
deenesjakoruzh
k-jarzyna

Miro MCP

by k-jarzyna
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

get-organization-member

Retrieve organization member details in Miro by providing organization and member IDs to access specific user information.

Instructions

Retrieves information about a specific organization member (Enterprise only)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orgIdYesid of the organization
memberIdYesid of the organization member

Implementation Reference

  • src/tools/getOrganizationMember.ts:13-22 (handler)
    The handler function that implements the core logic of the 'get-organization-member' tool. It fetches the organization member details using the MiroClient API.
    fn: async ({ orgId, memberId }) => {
  try {
    const response = await MiroClient.getApi().enterpriseGetOrganizationMember(orgId, memberId);

    return ServerResponse.text(JSON.stringify(response.body, null, 2));
  } catch (error) {
    process.stderr.write(`Error retrieving organization member: ${error}\n`);
    return ServerResponse.error(error);
  }
}
  • src/tools/getOrganizationMember.ts:6-12 (schema)
    The ToolSchema definition including the tool name, description, and Zod input schema for orgId and memberId parameters.
    const getOrganizationMemberTool: ToolSchema = {
  name: "get-organization-member",
  description: "Retrieves information about a specific organization member (Enterprise only)",
  args: {
    orgId: z.string().describe("id of the organization"),
    memberId: z.string().describe("id of the organization member")
  },
  • src/index.ts:198-198 (registration)
    The registration of the get-organization-member tool in the ToolBootstrapper chain in the main index file.
    .register(getOrganizationMemberTool)

Tool Definition Quality

B3.3/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool retrieves information (implying read-only), but doesn't specify what information is returned, whether authentication is required, if there are rate limits, or what happens with invalid IDs. The '(Enterprise only)' hint adds some context about access restrictions, but overall behavioral details are insufficient for a mutation-free tool.

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 that communicates the core purpose upfront. Every word earns its place: 'Retrieves information' (action), 'about a specific organization member' (resource), '(Enterprise only)' (important restriction). There's no redundancy or unnecessary elaboration.

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 this is a read operation with 2 required parameters and no output schema, the description is minimally adequate. It covers the basic purpose and an important restriction (Enterprise only), but lacks details about return format, error conditions, or authentication requirements. The absence of annotations and output schema means the description should do more to compensate, but it only partially meets this need.

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 both parameters clearly documented in the schema. The description adds no additional parameter information beyond what the schema provides. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no parameter details in the description, which applies here.

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 information') and resource ('about a specific organization member'), making the purpose unambiguous. It distinguishes from sibling tools like 'get-organization-members' (plural) by specifying a single member. However, it doesn't explicitly differentiate from 'get-project-member' or 'get-specific-board-member' which have similar retrieval patterns for different resource types.

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

Usage Guidelines3/5

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

The description implies usage context with '(Enterprise only)', suggesting this tool is restricted to enterprise organizations. However, it provides no explicit guidance on when to use this tool versus alternatives like 'get-organization-members' (for listing all members) or 'get-project-member' (for project-specific members). The agent must infer usage from the tool name and limited contextual hint.

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