Skip to main content
Glama

List Assigned Members

list_assigned_members
Read-onlyIdempotent

Find your clients and the members you work with by name, email, or exact ID using query. Includes your currently authorized direct advisor clients and existing program or specialist assignments. Returns 20 people by default with relationship and access boundaries; finding a person does not grant access to all of their records. memberCount is the total matching count; returnedCount is this page. Follow nextCursor with the same query only when more results are needed. Never guess between multiple matches.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_assigned_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum members per page, default 20. A response-size budget can return fewer; follow nextCursor.
queryNoSearch authorized members by name words, email, or exact member ID. Prefer search when a person is named; never guess between multiple matches.
cursorNoCopy nextCursor from the previous page and keep the same query. Omit to start or restart.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive, so the description correctly focuses elsewhere and adds real value: default page size of 20, memberCount vs returnedCount distinction, cursor pagination, and the important boundary that finding a person does not grant access to all of their records. It does not describe ordering or what the relationship/access-boundary fields contain, so a 4 rather than 5.

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?

Front-loads what the tool does, then scope, then return/pagination behavior, then the disambiguation warning. It is dense but every sentence carries information; a light edit would split the run-on opening clause.

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

Completeness4/5

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

With no output schema, the description steps in to explain page size, the two count fields, and cursor reuse, which is what an agent needs to page correctly. The only remaining gap is what the returned relationship/access-boundary information looks like.

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% and each parameter is already documented thoroughly, including the cursor pattern and limit default. The description restates query-as-name/email/ID and the pagination rule without adding syntax or format detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb (find/list) and resource (clients and members you work with) and immediately scopes it to authorized direct advisor clients plus program/specialist assignments. It does not name a sibling such as get_client_profile or list_household_entities to differentiate itself, which keeps it short of 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 Guidelines4/5

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

Gives clear situational rules: prefer search when a person is named, follow nextCursor with the same query only when more results are needed, and never guess between multiple matches. It stops short of naming an alternative tool for the case where you already know exactly which record you want.

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.