Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Turn schedule on or off

set_schedule_enabled
Idempotent

Turn an existing research schedule on or off so future occurrences reflect the change while past occurrences stay unchanged.

Instructions

Turns an existing research schedule on or off. Future occurrences change; past ones do not.

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": {
      "schedule_id": "<schedule_id>",
      "is_enabled": "<is_enabled>"
    },
    "name": "set_schedule_enabled"
  }
}

Input Schema

NameRequiredDescriptionDefault
is_enabledYes
schedule_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare the mutation profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false), so the bar is lower. The description still adds real behavioral value by explaining the temporal scope of the change: future occurrences are affected, past ones are preserved. It does not mention permission requirements or error behavior for invalid IDs.

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, the core operation first and the temporal caveat second. Every clause carries information; nothing is redundant or buried.

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 simple two-parameter toggle with full annotation coverage and no output schema, the description covers purpose and side-effect scope adequately. The only meaningful omission is parameter-level meaning, which is left entirely to the schema.

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

Parameters2/5

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

Schema description coverage is 0% for two parameters, so the description is the only place semantics could be added — and it says nothing about schedule_id or is_enabled. The names are largely self-explanatory (a positive integer ID and a boolean toggle), which prevents a 1, but the description does not compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description pairs a specific verb ('Turns ... on or off') with a specific resource ('an existing research schedule'), so an agent can tell it apart from create_research_schedule or delete-style siblings. It stops short of naming any sibling explicitly, which keeps it at 4 rather than 5.

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

Usage Guidelines3/5

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

The word 'existing' implies this applies to already-created schedules rather than new ones, giving implied usage context. However, there is no explicit statement of when to use this versus create_research_schedule, no preconditions, and no exclusions.

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