Chorono

by codie1982

Overview Schema Source Related Servers Discussions Admin

add_sm_transition

Connects two states in a Chorono state machine with a transition fired by an event, a guard condition, or both; use from="*" to apply it from any state.

Instructions

Connect two states with a transition. Fires on event, when guard holds, or both. Use from="*" for a transition that applies from any state.

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": {
      "smId": "<smId>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "add_sm_transition"
  }
}

Input Schema

Name	Required	Description
`id`	No	Optional transition id (auto-generated if omitted)
`to`	Yes	Destination state id
`from`	Yes	Source state id, or "*" for any state
`smId`	Yes	State machine id
`event`	No	Event name that fires this transition
`blendMs`	No	Cross-fade duration in ms (0 = hard cut)
`guardOp`	No	Guard comparison operator
`priority`	No	Higher wins when multiple are eligible
`requestId`	No
`sessionId`	No
`guardParam`	No	Parameter name for a guard condition
`guardValue`	No	Guard comparison value (number/bool/string)
`expectedRevision`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 7, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations declare readOnlyHint=false and openWorldHint=false, so the mutation/local-only profile is already known. The description adds genuine domain behavior about firing conditions (event, guard, or both) and the any-state wildcard, but is silent on priority resolution across multiple eligible transitions, revision/concurrency handling via expectedRevision, and idempotency via requestId.

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?

Three short sentences, front-loaded with the core action and followed by firing semantics and the wildcard tip. No sentence is redundant and nothing is buried.

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?

For a 13-parameter mutation tool with no output schema, the description covers the essential concept but leaves out prerequisites (existing smId and states), concurrency/idempotency behavior, and the priority tie-break rule. An agent could call it but may misuse the optional parameters.

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 coverage is 77%, so the schema already documents most parameters well. The description adds interpretation for event, guard, and the from="*" wildcard, but says nothing about priority, blendMs, guardOp, or the revision/request parameters. Baseline 3 is appropriate.

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?

States a specific verb and resource: "Connect two states with a transition," and clarifies the triggering semantics (event, guard, or both). It is clearly distinguishable from siblings like add_sm_state or set_initial_state, though it never names them explicitly.

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 only usage guidance is the from="*" wildcard tip, which is a parameter convention rather than a statement of when to choose this tool over alternatives. It does not say that the state machine and both endpoint states must already exist, nor when to add a transition versus setting an initial state.

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

Deploy Server