Skip to main content
Glama
Sign In
mcp-server-smartsheet-rm

mcp-server-smartsheet-rm

by christianclaudio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Projects List Project Members

projects_list_project_members
Read-onlyIdempotent

List members assigned to a project, optionally filtered by membership level (member, viewer, reporter, scheduler, or editor), to review project access and roles.

Instructions

List members of a project.

OpenAPI: GET /projects/{project_id}/project_members (getProjectsProjectIdProjectMembers). Optional membership filter: member, viewer, reporter, scheduler, or editor. When omitted, membership defaults to member; pass another level to list those.

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": {
      "project_id": "<project_id>"
    },
    "name": "projects_list_project_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoResponse page to return, starting at 1 (default 1).
per_pageNoMaximum items per page, up to 1000 (default 20).
membershipNoMembership level to list: member, viewer, reporter, scheduler or editor.
project_idYesID of the project.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.3.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world, and non-destructive behavior. The description adds a key behavioral detail: when the membership parameter is omitted, it defaults to 'member', which affects what is returned. This is useful context beyond 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?

The description is front-loaded with the core purpose and includes the endpoint and filter details. It is reasonably concise, though the OpenAPI line is somewhat technical and could be considered extra.

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?

Given the tool's simplicity (list with pagination and filter), rich annotations, and the presence of an output schema, the description covers the critical behavioral detail about membership defaults. It lacks explicit sibling differentiation, but otherwise provides sufficient context for correct invocation.

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 the baseline is 3. The description adds meaning beyond the schema by clarifying that when membership is omitted (schema default null), it actually defaults to 'member' behaviorally, which is not stated in the schema.

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 states a specific verb and resource: 'List members of a project.' It is clear what the tool does, but it does not distinguish this from similar sibling tools like projects_list_project_users or projects_list_relationships_project_members.

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?

The description provides some guidance on the membership filter, including its default, which implies usage. However, it does not explicitly state when to use this tool versus alternatives, leaving selection to inference.

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

Deploy Server

Other Tools