Skip to main content
Glama
Sign In

Conecto

by chat.conecto
OverviewDiscussionsAdmin

Repeat a tool call

schedules_create

Run any tool on a timetable, e.g. a weekly report, a daily export or a reminder every Monday at 9:00, in the business's time zone. It runs as this bot, under its daily budget, and each run costs the tool's own price; the reply estimates the most it can cost a month. arguments are checked now; date words in them ({today}, {today+7}, {month}, {last_month}, {year}) are filled in at each run. For one run, use schedules_run_later. Tools that take tokens or read the vault can't be scheduled. A schedule is $0.50 a month, renewed from the balance; the first month is this call. Five failed runs in a row pause it and email the owner. Costs $0.50 per call; nothing if it fails.

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": {
      "name": "<name>",
      "tool": "<tool>",
      "timetable": "<timetable>"
    },
    "name": "schedules_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYese.g. "Monday invoice reminders".
toolYesThe tool to run, e.g. "invoices_remind".
argumentsNoThe tool's arguments, as you would send them.
time_zoneNoe.g. "America/Los_Angeles". The business calendar's time zone if left out, else UTC.
timetableYesWhen it runs, in time_zone. {"every": "minutes", "interval": 30} (15 at the least, 60 for tools that contact people or sites outside the business); {"every": "hour", "interval": 1, "minute": 0}; {"every": "day", "at": "09:00"}; {"every": "week", "days": ["mon", "thu"], "at": "09:00"}; {"every": "month", "day": 1, "at": "09:00"} (day 1 to 28, or "last").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations (which only say non-read-only, non-idempotent, non-destructive) by disclosing cost ($0.50/month, first month charged now), budget accounting, failure policy (five consecutive failures pause and email the owner), and that arguments are validated now while date placeholders expand at run time. That is substantial operational context an agent needs before creating a schedule.

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

Conciseness4/5

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

Purpose and the alternative are front-loaded, and every sentence carries useful information. Minor redundancy: the $0.50 cost is stated twice ('$0.50 a month... the first month is this call' and 'Costs $0.50 per call'), which slightly inflates the length.

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?

For a nested-object mutation tool with no output schema, the description covers cost, failure/suspension behavior, budget, time-zone default, argument validation timing, and tool eligibility. Nothing an agent needs to call it correctly is missing.

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% and the nested timetable schema already documents 'every'/'at'/'day'/'days' with examples, so baseline is 3. The description adds value the schema lacks: the supported date placeholders ({today}, {today+7}, {month}, {last_month}, {year}) in arguments and that they resolve per-run, which materially affects how to fill the arguments 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 action (run any tool on a timetable) with concrete examples (weekly report, daily export, Monday reminder) and immediately names the sibling it is not ('For one run, use schedules_run_later'). An agent can distinguish this from schedules_run_later and schedules_update without opening a 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?

Explicitly routes the single-run case to schedules_run_later and states exclusions ('Tools that take tokens or read the vault can't be scheduled'). This gives both when-to-use and when-not-to-use with a named alternative.

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

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