Skip to main content
Glama

Coline

Ask a crew member

message_crew_member

Asks a crew member to do something: posts in their direct message as the person, which starts their work. Use it when the person wants a crew member on a task.

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>",
      "agentUserId": "<agentUserId>",
      "text": "<text>"
    },
    "name": "message_crew_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
agentUserIdYesCrew member id from list_crew.

Output Schema

NameRequiredDescriptionDefault
urlYes
messageIdYes
conversationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.7/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false, idempotentHint=false), so the description's added context is what matters: the post appears as the person and it triggers the crew member's work. That impersonation and side-effect disclosure is exactly the behavior an agent needs before invoking a non-idempotent write. It does not cover what happens if the crew member is unavailable or how the work is tracked afterward.

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 short sentences, front-loaded with the action and followed by the key side effect and the usage condition. No filler or repetition of the annotations, though the colon construction is slightly compressed rather than fully polished.

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 no explanation. For a 3-parameter, non-idempotent write the description covers action, mechanism, and trigger condition adequately. Missing are failure or duplicate-send behavior and any prerequisite about the crew member's availability, which are the remaining gaps.

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 coverage is 67%: workspace and agentUserId carry their own descriptions and provenance hints (workspaces.list, list_crew). The undocumented parameter is text, whose meaning ('the task instruction') is only implied by the description's first clause, with no guidance on the 12,000-character limit or what content shape is effective.

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?

States a concrete verb and resource (asks a crew member to do something) and explains the mechanism: a direct-message post made as the person that starts their work. That mechanism distinguishes it from the many plain messaging siblings such as send_message or edit_message, although no sibling is named explicitly.

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?

Gives one positive usage cue ('use it when the person wants a crew member on a task'), which is enough to imply intent. It offers no when-not condition and does not distinguish this from ordinary messaging tools, so the agent must infer that routing a plain message belongs elsewhere.

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