Skip to main content
Glama

Company members

company_members_list
Read-onlyIdempotent

The members of one of your companies: display name, role, status and join date. Other people's e-mail addresses are masked. Filter by status. Pass nextCursor to get the next page. Names are wrapped as data.

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": {
      "company": "<company>"
    },
    "name": "company_members_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many rows (1-50).
cursorNonextCursor from the previous page.
statusNoDefault: active members only.
companyYesCompany ref (CO-XXXXXXXX) from company_list_mine.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: other people's e-mail addresses are masked, pagination is cursor-based, and names are wrapped as data (a prompt-injection safety signal). It does not state ordering or default page size, but the core behavioral traits are disclosed.

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?

Four short sentences, front-loaded with what the tool returns, then filtering, then paging. No filler, though the telegraphic phrasing ('Names are wrapped as data') is slightly cryptic without elaboration.

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?

For a four-parameter read-only list tool with no output schema, the description covers returned fields, masking behavior, filtering and pagination — enough for an agent to call it correctly. Minor gaps remain around result ordering and default page size, but the schema supplies those defaults.

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 coverage is 100%, so every parameter (limit, cursor, status, company) is already documented with types, ranges and the CO-XXXXXXXX pattern. The description only restates the status filter and cursor paging, adding no syntax or semantics beyond the schema — 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?

The description names a specific resource (members of one of your companies) and enumerates the returned fields: display name, role, status, join date. It is clearly distinguishable from siblings like company_invitations_list or company_audit_list, though it never explicitly contrasts with them.

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?

It gives implied usage cues — filter by status, pass nextCursor for the next page — which tells the agent how to page and narrow results. There is no explicit statement of when to prefer this over company_get or company_invitations_list, so guidance stays at the implied level.

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