Skip to main content
Glama

get-member-list

Read-onlyIdempotent

Search all members across the Dooray organization to find a person's organizationMemberId, name, user code, or email—useful for adding someone outside the current project as a CC by email or member ID.

Instructions

Search members across the whole Dooray organization (조직 전체 멤버 검색).

Unlike get-project-member-list, this is not limited to one project. Use it to find the organizationMemberId of someone outside the project (e.g. to add them as CC by email or member ID).

Search Conditions (combine as needed):

  • name: Member name

  • userCode: User ID, like match

  • userCodeExact: User ID, exact match

  • externalEmailAddresses: Email addresses, exact match only (not a like search)

  • idProviderUserId: SSO user ID (e.g. employee number)

Examples:

  • By name: {"name": "홍길동"}

  • By email: {"externalEmailAddresses": ["user@example.com"]}

  • By user ID: {"userCodeExact": "gildong.hong"}

Returns: totalCount and members with id (organizationMemberId), name, userCode, externalEmailAddress. Use get-member for full details.

Input Schema

NameRequiredDescriptionDefault
nameNoMember name
pageNoPage number (default: 0)
sizeNoItems per page (default: 20, max: 100)
userCodeNoUser ID (like match)
userCodeExactNoUser ID (exact match)
idProviderUserIdNoSSO user ID (e.g. employee number)
externalEmailAddressesNoEmail addresses (exact match)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, covering the safety profile. The description adds valuable behavioral context: it explains that some parameters are exact-match only (e.g., externalEmailAddresses) while others are like-search, and specifies the return fields (totalCount, members with id/name/userCode/externalEmailAddress). It also points to get-member for full details. This goes beyond annotations, though it could mention rate limits or auth.

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 front-loaded with purpose and sibling differentiation, followed by a clear list of search conditions, examples, and return information. Every sentence serves a purpose: no repetition, no fluff. The structure is logical and easy to parse.

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

Completeness5/5

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

Given the tool's complexity (a read-only search across organization members), the description covers purpose, usage guidelines, parameter semantics, and return values. Annotations cover safety, and the description fills in the rest. No output schema is present, but the return shape is described. Nothing essential is missing.

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

Parameters4/5

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

Schema description coverage is 100%, so baseline is 3. However, the description adds examples that show how to combine parameters for common searches (by name, email, user ID), which is helpful beyond the schema. It also clarifies that externalEmailAddresses uses exact match only (though this is already in the schema), adding marginal value. The examples make it a 4.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb (Search) and resource (members across the whole Dooray organization), explicitly distinguishes it from sibling tool get-project-member-list, and provides a concrete use case (finding organizationMemberId for someone outside the project). An agent can immediately tell what the tool does and when it applies.

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

Usage Guidelines5/5

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

The description explicitly says 'Unlike get-project-member-list, this is not limited to one project' and gives the exact scenario: 'Use it to find the organizationMemberId of someone outside the project (e.g. to add them as CC by email or member ID).' This clearly routes the agent between this and related tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.