Skip to main content
Glama

Coline

Send a task outside

hand_task_outside
Destructive

Emails someone outside the workspace to do a task, from your address or the board's, and the task then waits on them until they deliver. Write the email yourself (or draft it first). Mail leaving the workspace follows the usual rules; a crew member's follows the crew email rules.

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>",
      "taskboardId": "<taskboardId>",
      "taskId": "<taskId>",
      "to": "<to>",
      "subject": "<subject>",
      "body": "<body>"
    },
    "name": "hand_task_outside"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
bodyYes
fromNome
taskIdYes
dueDateNo
subjectYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
taskboardIdYes

Output Schema

NameRequiredDescriptionDefault
typedYes
handoffIdYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, non-idempotent and not read-only, so the safety profile is largely covered. The description adds real context beyond that: the mail leaves the workspace and is subject to external-mail and crew-email rules, and the task enters a waiting state. It omits what is irreversible (external delivery cannot be recalled), whether the task state is reverted on failure, and any rate or moderation constraints.

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 the action and its consequence, and no filler. The parenthetical "(or draft it first)" is slightly loose but does not obstruct. Nothing is buried behind preamble.

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?

For a destructive, open-world mutation with six required parameters and a nested recipient object, the description covers the core model (external email plus a task waiting on the recipient) and an output schema exists so return values need no explanation. Gaps remain around failure/rollback behavior and the eligibility rules alluded to only in passing.

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?

Schema description coverage is only 13% across eight parameters, so the description needs to compensate and mostly does not. It does explain the `from` enum semantically ("from your address or the board's") and implies subject/body are authored by the caller, but taskId, taskboardId, workspace, dueDate and the nested recipient `name`/`email` object are left entirely to 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?

States a specific action verb and resource: "Emails someone outside the workspace to do a task ... and the task then waits on them until they deliver." That is materially different from a plain send_mail and an agent can tell what will exist afterwards (an outbound email plus a task blocked on a third party). It stops short of naming the plain-send siblings it must be distinguished from.

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?

"Write the email yourself (or draft it first)" gives practical context on how to invoke it, and the closing sentence hints at eligibility rules ("a crew member's follows the crew email rules"). But there is no explicit when-to-use/when-not guidance versus send_mail or send_message, and no stated preconditions such as permissions or whether the recipient must be unknown to the workspace.

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