Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

List people on a site

site_people_list
Read-onlyIdempotent

Who can open this site: workspace members with their level, guests, members without access (withoutAccess), and pending invites. youAreMember tells whether you may invite members (not only guests). site_people.invite, site_people.set_level and site_people.revoke_invite change them.

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": {
      "siteId": "<siteId>"
    },
    "name": "site_people_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the description correctly does not repeat those. It adds useful behavioral context by explaining that results include access levels, no-access members, pending invites, and a youAreMember permission indicator, though it omits pagination or result-size details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences are front-loaded with the returned access categories, followed by the permission flag and mutation alternatives. Every sentence carries useful information without redundant framing.

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 one-parameter read tool with no output schema, the description covers the returned categories and the youAreMember permission meaning well. The main gap is that siteId and pagination behavior are never explained, but the definition is otherwise sufficient to call the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The only parameter, siteId, has 0% schema description coverage, and the description says only 'this site' without explaining its format, source, or whether it is an ID or domain. It adds almost no meaning beyond the parameter name.

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?

The description states the exact access roster returned: workspace members with their level, guests, members without access, pending invites, and the youAreMember flag. It also contrasts this read operation with site_people.invite, set_level, and revoke_invite, which change those people.

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?

It clearly implies use when auditing who can open a site and explicitly points to the mutation tools for changing access. However, it does not say when to choose this over other list-oriented siblings such as members_list or shares_list.

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