Skip to main content
Glama
Sign In

Sivella

by ai.sivella.mcp
OverviewDiscussionsAdmin

Block out time

create_availability_block

Block off time on the CALLER'S OWN calendar as busy (not a shared event). Commits immediately.

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": {
      "starts_at": "<starts_at>",
      "ends_at": "<ends_at>"
    },
    "name": "create_availability_block"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoOptional private label for the actor's own block.
ends_atYesDate and time, ISO 8601 (e.g. '2026-06-10T14:00').
starts_atYesDate and time, ISO 8601 (e.g. '2026-06-10T14:00').
visibilityNoshared = household sees the block title; generic = household sees an opaque 'Busy' block (default); hidden = only the owner sees it, not counted as busy.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the description's job is to add context beyond that — and it does, by disclosing that the write is immediate with no confirmation step and that it affects only the caller's calendar. It stops short of saying whether the block can later be cancelled or how it behaves against an existing conflicting event.

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?

Two short sentences, with the ownership scope and the non-shared-event caveat front-loaded before the immediacy note. There is no filler and nothing an agent must read past to reach the essential facts.

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 four-parameter mutation tool with no output schema, the definition covers the essential behavioral facts: whose calendar, what visibility model, and that the write is immediate. Minor gaps remain around conflict handling with existing events and what the call returns, but these are not blocking for correct invocation.

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 description coverage is 100% and the visibility enum already explains shared/generic/hidden semantics, so the schema carries the parameter burden. The description reinforces the ownership/private-label framing but adds no format or default detail beyond what the schema states, making the baseline 3 appropriate.

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 gives a specific verb and resource ('Block off time on the CALLER'S OWN calendar') and immediately scopes it against the obvious confusion ('not a shared event'), which separates it from create_household_event. 'Commits immediately' further characterizes the operation, so an agent knows exactly what this call does without opening the 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?

The negative scope statement ('not a shared event') effectively tells the agent when this tool is the wrong choice and implies create_household_event is the alternative. However, it never names that sibling or states an explicit 'use X instead when you want others to see it' rule, so routing is inferred rather than spelled out.

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

All Sivella 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