Skip to main content
Glama

Set yourself away

fleet__set_away
Idempotent

Mark the signed-in user away from their desk in this agency, or back, for example when they say they are heading out. While away, Royally emails them about changes waiting for their approval. Changes only their own setting; it cannot approve anything.

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": {
      "away": "<away>"
    },
    "name": "fleet__set_away"
  }
}

Input Schema

NameRequiredDescriptionDefault
awayYestrue to mark the user away, false when they are back.
hoursNoHow many hours to stay away before it turns off on its own. Omit or null for until they turn it off.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new behavior: while away the system emails the user about changes awaiting their approval, and the setting affects only their own account. It does not say whether email is immediate or throttled, but the key side effect is disclosed.

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?

Three short sentences, front-loaded with the action, then the side effect, then the scope limit — each carries information. Minor slack in phrasing like "in this agency" and the example clause, but nothing is redundant enough to cut.

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 two-parameter, non-destructive toggle with no output schema and full annotation coverage, the description supplies the important missing pieces: the notification side effect and the self-only scope. Return value behavior is not needed here since the outcome is a simple state change.

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 100%, and the schema already explains both the boolean toggle and the 1–168 hour auto-off window, so the baseline is 3. The description adds no format, default, or interaction detail about `away` or `hours` beyond what the schema states.

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 names a specific verb and object: mark the signed-in user away from their desk, or back. It also bounds the scope ("Changes only their own setting") and explicitly disclaims approval behavior, which separates it from approval-oriented siblings such as fleet__continue_call and fleet__deny.

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 gives a concrete when-to-use trigger ("when they say they are heading out") and an implicit when-not ("it cannot approve anything"), so the agent knows this is not an approval tool. It stops short of naming an alternative tool or stating exclusions explicitly, so it is clear context rather than a full routing 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