Skip to main content
Glama
Sign In

Mycel

by com.mycelhq
OverviewDiscussionsAdmin

change_timing

Change when a recurring job runs, in plain words: 'push it to the 15th', 'skip October', 'quarterly from now on'. Unclear requests are refused with a question.

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": {
      "job_id": "<job_id>",
      "instruction": "<instruction>"
    },
    "name": "change_timing"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesThe job's id, from list_recurring_work.
instructionYesThe change, in plain words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load. It does disclose one genuinely valuable and non-obvious behavior: unclear requests are refused with a question rather than silently applied. However, it says nothing about permissions, reversibility, what happens to already-scheduled occurrences, or what a successful change returns.

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 sentences, front-loaded with the verb and resource, then examples that earn their place by defining the input grammar. No filler or restated boilerplate.

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

Completeness3/5

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

The tool is simple (two params, one free-text) and the description covers purpose, input style, and the ambiguity-handling path, which is the main risk. It still leaves the agent unsure about the outcome of a successful change and whether to verify with list_recurring_work afterwards.

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?

Schema coverage is 100%, so the baseline is 3, but the description earns a bump by illustrating the accepted class of values for 'instruction' — date shifts, skipped occurrences, cadence changes — which the schema's terse 'The change, in plain words' does not convey.

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 with scope: 'Change when a recurring job runs'. Concrete instruction examples ('push it to the 15th', 'skip October', 'quarterly from now on') pin down the domain of change, making it clearly distinct from read-side siblings like list_recurring_work.

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?

Usage is implied rather than stated: an agent can infer this is the tool for rescheduling an existing recurring job, but there is no explicit when-to-use vs when-not guidance or named alternatives (e.g., creating a new job instead). The note about phrasing the request 'in plain words' is helpful invocation guidance.

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

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