Retrieve all members of a TestMonitor project to identify who has access to project resources and their assigned roles.
Get all project members. Retrieve all members of a project. Project members have access to the project's resources and can perform actions based on their roles.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | ||
| query | No |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is fully covered. The description adds only mild domain context (members have access and act via roles), and says nothing about pagination behavior or authorization requirements, so it barely clears the bar set by 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is short, but the first two sentences are near-verbatim restatements ('Get all project members' / 'Retrieve all members of a project'), so one of them does not earn its place. The remaining sentence is background rather than operational detail.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a read-only, paginated collection endpoint with no output schema, the description should convey return shape (what a member record contains) and pagination behavior. It gestures at member semantics but omits pagination and any note on ordering or result envelope.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description mentions none of the inputs: the nested path.projectId, or the query.page/limit pagination parameters. With schema description coverage reported at 0%, the description needed to compensate for parameter semantics and does not.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a clear verb+resource: 'get all project members' / 'retrieve all members of a project.' The purpose is unambiguous, but it never distinguishes this tool from similar collection tools such as get_team_members, get_user_collection, or get_project_collection in the sibling list.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool, when not to, or which alternative to pick (e.g., team members vs. project members). The third sentence describes the domain concept of a member but gives no invocation context or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.