Skip to main content
Glama

GetOrganizationMembers

Read-onlyIdempotent

List the members of a GraphOS organization with each member's user ID, name, and email. UpdateProposalReviewers takes these user IDs. Match the person the user named, by email when names are ambiguous, and do not list the other members back to the user. The list is not paginated, so a large organization returns every member. This tool needs the GraphOS sign-in (OAuth) or a personal API key in the x-api-key header. A graph key cannot read the members and gets NOT_ALLOWED_BY_USER_ROLE. Provide the organization ID, which GetMyIdentity returns.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "organizationId": "<organizationId>"
    },
    "name": "GetOrganizationMembers"
  }
}

Input Schema

NameRequiredDescriptionDefault
organizationIdYes

Output Schema

NameRequiredDescriptionDefault
dataNo
errorsNo
extensionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, but the description adds genuinely new operational facts: the result set is unpaginated and can be large, OAuth sign-in or a personal API key in x-api-key is required, and a graph key fails with NOT_ALLOWED_BY_USER_ROLE. That is precisely the auth and scale information an agent cannot get from the annotations.

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?

Purpose leads, then workflow routing, then behavioral limits, then prerequisites, then parameter sourcing — a sensible front-loaded order. A few clauses (e.g. re-stating that each member has an ID, name, and email when the output schema already exists) are mildly redundant, but nothing is padding.

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?

For a single-parameter read tool with an output schema already present, the description covers everything left open: auth mode, a named error for the wrong credential type, absence of pagination, and how to obtain the required ID. No behavioral or selection question an agent would have is left unanswered.

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 coverage is 0% for the single organizationId property, so the description carries the burden and does so by naming its provenance ("which GetMyIdentity returns"). It stops short of stating the ID's format or an example, leaving a small gap, but the practical question of where to obtain the value is answered.

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?

Opens with a specific verb and resource ("List the members of a GraphOS organization") and names the returned fields (user ID, name, email), which also implicitly separates it from GetMyIdentity, the sibling used to obtain the caller's own identity. An agent can distinguish this from every other Get* sibling without opening a schema.

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?

Explicitly routes the agent to UpdateProposalReviewers as the consumer of these user IDs, tells it how to disambiguate (match by email when names are ambiguous), instructs it not to echo other members back, and points to GetMyIdentity as the source of the required organization ID. When-to-use, what-to-do-with-results, and prerequisite discovery are all covered.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources