Skip to main content
Glama
Sign In

Conecto

by chat.conecto
OverviewDiscussionsAdmin

Run a tool call once, later

schedules_run_later

Run one tool call once at a set time: "send this Tuesday at 9:00", "check on Friday whether invoice 42 was paid". Give at (ISO 8601 with its offset, up to a year ahead) or in_minutes. It runs as this bot, under its daily budget, and costs the tool's own price when it runs, plus $0.01 now; no monthly rent. Date words in arguments ({today}, {today+7}, {month}, {last_month}, {year}) are filled in when it runs, in time_zone. schedules_list shows it; schedules_delete cancels it before it runs. Costs $0.01 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": {
      "tool": "<tool>"
    },
    "name": "schedules_run_later"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNoe.g. "2026-10-20T09:00:00-07:00".
nameNoe.g. "Monday invoice reminders".
toolYesThe tool to run, e.g. "email_send".
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.
in_minutesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: it runs as this bot under its daily budget, costs $0.01 now plus the tool's own price at run time, is refunded on failure, is capped at one year ahead, and supports {today}/{month}/{last_month} template substitution resolved at run time in time_zone. None of that is derivable from the non-readOnly, non-destructive annotations.

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?

Front-loaded with the core action and examples, and every clause is informative. The cost point is stated twice ('plus $0.01 now' and 'Costs $0.01 per call; nothing if it fails'), a small redundancy that keeps it from a 5.

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?

No output schema exists, and the description covers scheduling semantics, billing, failure behavior, and lifecycle siblings well enough to invoke it correctly. It never says what the call returns (e.g., a schedule ID), which is the one remaining gap for a creation tool.

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 already 83%, so the baseline is 3; the description goes further by specifying ISO 8601 with offset and a one-year horizon for 'at', the in_minutes alternative, and how time_zone governs date-word resolution in arguments. The 'arguments' nested object's template behavior is explained, which the schema itself does not cover.

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 with explicit scope: 'Run one tool call once at a set time,' and the 'once' plus examples ('send this Tuesday at 9:00') cleanly separate it from recurring siblings like schedules_create and from schedules_list/schedules_delete.

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?

Gives concrete usage examples and states the two ways to set the timing (at or in_minutes), plus routes the agent to schedules_list for viewing and schedules_delete for cancellation. It never explicitly contrasts with schedules_create for recurring schedules, but 'once' implies the distinction.

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