Skip to main content
Glama

Coline

Show crew

show_crew
Read-onlyIdempotent

Shows the workspace's crew inside the chat: who's working on what, what waits on the person, and a way to ask each of them for something.

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_crew"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
agentUserIdNoOpen this crew member.

Output Schema

NameRequiredDescriptionDefault
crewYes
openYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful framing about what the view surfaces (who's working on what, what waits on the person), but "a way to ask each of them for something" risks reading as a messaging action, which sits awkwardly with a read-only annotation and is never clarified.

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

Conciseness3/5

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

It is a single front-loaded sentence with no filler, which is good, but the final clause ("a way to ask each of them for something") introduces ambiguity rather than information and could be cut or replaced with a concrete statement of behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema and full annotation set carry much of the burden, so the description does not need to explain return values. It still leaves key gaps for a tool whose name suggests a view: whether it opens a UI surface or returns data, and what the agentUserId scoping does.

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 description coverage is 100%, with both workspace and agentUserId fully documented in the schema, so the baseline is 3. The description adds nothing about either parameter, such as what scoping by agentUserId changes in the view.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

It names a verb and resource ("Shows the workspace's crew") but qualifies it with "inside the chat," so it is unclear whether the tool returns crew data or renders a UI panel in the conversation. The trailing phrase "a way to ask each of them for something" muddies the purpose further rather than sharpening it, and nothing distinguishes it from other crew-related capabilities.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to reach for this tool, when not to, or what a preferred alternative would be. The only implicit usage cue is "inside the chat," which is a location hint rather than a selection rule.

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