Skip to main content
Glama

Coline

Show members

show_members
Read-onlyIdempotent

Shows a team workspace's members inside the chat with Coline's members page: everyone and their roles, pending invites, and inviting someone. Use it when the person wants to see or manage who's in the workspace.

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": {
      "workspace": "<workspace>"
    },
    "name": "show_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
urlYes
membersYes
workspaceYes
pendingInvitesYes
canManageMembersYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: the output is an interactive in-chat page with roles and pending invites. However, "inviting someone" sits uneasily beside readOnlyHint=true and is never clarified (the page offers the action vs. the tool performing it), which leaves a small ambiguity an agent may misread as a write capability.

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?

Two sentences, front-loaded with what the tool shows, followed by the usage trigger. Every clause carries information (contents of the page, delivery mode, trigger). Slight redundancy between "members" in the first clause and "everyone and their roles" later.

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?

An output schema exists, so return values need not be described, and the single parameter is fully documented in the schema. For a low-complexity UI-surface tool the description is nearly complete; only the inviting-versus-read-only nuance and any workspace-access prerequisites are left unaddressed.

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?

Single parameter with 100% schema description coverage, including format and provenance ("Workspace slug from workspaces.list, e.g. \"acme\""). The description only says "team workspace" and adds no format or resolution detail beyond the schema, so the documented baseline of 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?

Names a specific verb and resource ("Shows a team workspace's members") and adds the distinguishing delivery mode: it opens Coline's members page inside the chat rather than returning raw data. What the page contains (roles, pending invites, inviting) is spelled out, so the agent can picture the result. It does not explicitly contrast with a data-returning member list, but the rendering mode is clear from the text itself.

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 a concrete trigger: "Use it when the person wants to see or manage who's in the workspace." That covers both viewing and managing intent, which is broader than a pure read tool. No when-not conditions or prerequisites (e.g. needing a valid workspace slug) are stated, but the trigger is unambiguous.

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