Skip to main content
Glama
Sign In

Marsell

by com.getmarsell
OverviewDiscussionsAdmin

Slot drop

slot_drop
Destructive

Take an open slot (a planned piece on a later day) off the calendar when it no longer makes sense. Say why in plain words; the owner reads it. A task already in the week ahead is taken off with work_cancel instead. 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>",
      "reason": "<reason>"
    },
    "name": "slot_drop"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesThe open slot's key (situation_read calendar).
reasonYesWhy it comes off, 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.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the removal semantics are partly covered; the description adds that this is a calendar removal, that the supplied reason is read by the owner (i.e. it is user-visible justification, not internal telemetry), and that an act key is needed. It does not say whether the dropped slot can be restored with slot_add or what the response contains, which keeps it from a 5.

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

Conciseness5/5

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

Three short sentences, front-loaded with the action, then the reason, then the alternative. Nothing is filler and the sibling diversion is placed where it is needed.

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 three-parameter destructive tool with no output schema, the description covers what it does, why the reason matters, and the alternative path. The only meaningful gap is recoverability — whether a dropped slot can be brought back via slot_add — which matters for a destructive operation.

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 description's statements about the key and the plain-words reason largely restate the schema property descriptions. It adds the framing that the reason is read by the owner, but no guidance on the optional project parameter or on key sourcing beyond what the schema already says.

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 states a specific verb and resource ('Take an open slot ... off the calendar') and immediately defines what a slot is ('a planned piece on a later day'), so the scope is unambiguous. It also contrasts with the nearest sibling by pointing at work_cancel for tasks already in the week ahead.

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

Usage Guidelines5/5

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

It gives the triggering condition ('when it no longer makes sense') and an explicit carve-out routing a different case to work_cancel. An agent can pick between this and work_cancel without opening either schema.

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