Skip to main content
Glama
Sign In

Well

by io.github.WellApp-ai
OverviewDiscussionsAdmin

List schedule triggers

well_list_schedule_triggers
Read-onlyIdempotent

List the events Well can start a routine on, each with what it means and the details it carries.

Use it when the user wants a routine to start each time, or as soon as, something happens, instead of at a set time ("send me a poem at 1:45am") or on a rhythm, which need no trigger. Each entry carries a trigger (the value for well_create_schedule's trigger_name), a description of what happened and when it fires, and params (the event details the run receives, by name). The list is empty when Well sends no event yet.

When one entry fits what the user described, create the routine with that trigger_name and no cron_expression, and describe the event in the cadence_label in plain words. When none fits, say that Well cannot start a routine on that event yet and offer a clock rhythm. Never say a trigger name to the user.

Input Schema

NameRequiredDescriptionDefault
workspace_idNoTarget workspace. Optional: this tool describes the token itself rather than one workspace's data, so omitting it returns the same answer.
conversation_idNoThe conversation id returned by the previous Well result, in its meta under well/conversation_id, in its structuredContent, or in its JSON text block. Pass it back on every call in the same conversation, including a call a card makes, so the chosen workspace and the earlier answers still apply. It decides the conversation on its own: nothing the host states about the session replaces it. Omit it only on the first call of a conversation.
workspace_scopeNoRestrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace.

Output Schema

NameRequiredDescriptionDefault
successYes
triggersYes
conversation_idNoThe conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.
newly_connectedNoTools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: "<name> is connected.". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later.
conversation_id_noteNoPresent only when the server opened a fresh lane, stating that no choice recorded earlier was read.
conversation_id_sourceNoWhere the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / newly_connected / description
      Previous value: -"Tools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. Start the reply with one line per entry, in the person's language: \"<name> is connected.\". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later."New value: +"Tools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: \"<name> is connected.\". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later."
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, and the description still adds real context: each entry's shape (trigger value, description, params by name) and the empty-list edge case when Well has sent no event. It stops short of stating read-consistency or refresh behavior, but the added detail goes beyond what the annotations declare.

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 purpose, then when-to-use, then the create-routine workflow, with no filler sentences. It is on the long side and the parenthetical 'send me a poem at 1:45am' is illustrative rather than essential, but every sentence carries actionable instruction.

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 and the schema covers all three optional params, so the description's remaining burden is routing and edge cases — both present (alternatives to triggers, the empty-list state, the downstream create call). Nothing needed to call this correctly is missing.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents workspace_id, conversation_id, and workspace_scope in depth. The description contributes no additional parameter syntax or format guidance, so this is the baseline 3 for a schema doing the heavy lifting.

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+resource: 'List the events Well can start a routine on', and enumerates what each entry contains (trigger, description, params). An agent can distinguish it from well_create_schedule and well_list_schedules without opening either schema, since this one only reads the catalog of available triggers.

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 names the when ('the user wants a routine to start each time, or as soon as, something happens'), the when-not ('instead of at a set time ... or on a rhythm, which need no trigger'), and the downstream alternative (well_create_schedule with cron_expression). It even prescribes what to do when no entry fits and forbids naming trigger names to the user.

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

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