Skip to main content
Glama
Sign In
calendula

calendula

by mkyutani
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

start_outlook

Idempotent

Launches Outlook (classic) when calendar reads fail because it is not running, opening a desktop window without closing it afterward. Use only after user approval.

Instructions

Start Outlook (classic) if it is not running. It never closes Outlook.

It opens a window on the user's desktop. Call it only after the user has agreed, and only after a fetch failed because Outlook is not running.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "start_outlook"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, so the safety profile is covered structurally. The description adds context annotations cannot convey: a window appears on the user's desktop and the tool never closes Outlook. It stops short of describing failure behavior (e.g., what happens if startup fails), so it is strong rather than complete.

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?

Four short sentences, each earning its place: identity/condition first, then the non-closing guarantee, then the visible side effect, then the invocation precondition. Front-loaded and waste-free.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and the tool is a zero-parameter, low-complexity action. Everything an agent needs to decide whether to call it and what user-visible effect to expect is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. The description correctly avoids restating the empty argument object.

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 ('Start Outlook (classic)') plus a scoping condition ('if it is not running'). The clarification 'It never closes Outlook' separates it from a restart-style sibling without the agent needing to open another schema.

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?

Gives an explicit precondition chain: only after the user has agreed, and only after a fetch failed because Outlook is not running. That is a concrete when-to-use and implicit when-not-to-use rule, not merely implied usage.

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

Deploy Server

Other Tools