Skip to main content
Glama
Sign In

Marsell

by com.getmarsell
OverviewDiscussionsAdmin

Slot move

slot_move

Move an open slot to another later day of the calendar (after the week ahead, within the horizon). To bring one into the week ahead, write its full task under its key with work_plan instead. Say why in plain words. It needs an act key.

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": {
      "key": "<key>",
      "date": "<date>",
      "reason": "<reason>"
    },
    "name": "slot_move"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesThe open slot's key (situation_read calendar).
dateYesIts new day, YYYY-MM-DD: after the week ahead ends, on or before the horizon's end.
reasonYesWhy it moves, in plain words; the owner reads it.
projectNoThe project's id or exact name. Optional when the account has one project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations (readOnly=false, destructive=false), the description discloses two non-obvious behaviors: the move is forward-only (a later day, past the week ahead, inside the horizon), and the supplied reason is surfaced to the owner, which shapes what should be written. It does not say whether the slot keeps its key/content or whether the move is reversible.

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?

Four short sentences with the core action and its scope front-loaded, and the alternative routing immediately after. The final two fragments ("Say why in plain words. It needs an act key.") partly restate the schema's own parameter descriptions and read as telegraphic padding.

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 non-destructive mutation with full schema coverage, no output schema, and annotations covering the safety profile, the description supplies the scope limits and the reason's audience. Only the post-move effects (key retention, undoability, confirmation) are left unstated.

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%, so the key/date/reason/project semantics and the YYYY-MM-DD and horizon boundaries are already documented. The description only echoes this at a high level ("It needs an act key", "Say why in plain words") without adding new meaning, so baseline 3 applies.

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?

States a specific verb and resource ("Move an open slot") plus the exact scope: a later day, after the week ahead, within the horizon. The parenthetical constraint and the pointer to work_plan let an agent distinguish this from the sibling without opening either schema.

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?

"To bring one into the week ahead, write its full task under its key with work_plan instead" gives an explicit when-not rule and names the alternative tool. Other plausible alternatives (slot_add, slot_drop, work_reschedule) are not differentiated, so the routing guidance is strong but not exhaustive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Marsell toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources