Skip to main content
Glama
Sign In

Umtri

by io.umtri
OverviewDiscussionsAdmin

Create a new season

create_season

Creates a new season and makes it the "now" season. This is not an additive act: the ground's current now-season is sealed as past and every node in it is marked grown, which locks that node's parent/season/type/sproutedAt. CONFIRMATION GATE: call once WITHOUT confirm to get back what would be sealed, put that to the user in your own words, and call again with confirm:true only after they say yes. Never pass confirm:true on your own judgment — a season is the human's declaration that one chapter closed and the next began, and inventing one makes the ground's timeline meaningless. Unsure which season a node belongs to? Attach it to the existing now-season instead of opening a new one. See umtri://rules/seasons.

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": {
      "slug": "<slug>",
      "label": "<label>"
    },
    "name": "create_season"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesGround slug.
labelYesSeason label the human chose — a version, phase, or period (e.g. "1.0.0", "PoC", "Q3 2026").
confirmNoPass true ONLY after the user has agreed to this exact season. Omit it on the first call to receive the confirmation payload instead.

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?

No annotations are supplied, so the description carries the full burden and does so: it discloses that the operation is destructive to the prior now-season (sealed as past, all its nodes marked grown and their parent/season/type/sproutedAt locked), which fields get frozen, and what the first non-confirming call returns. This is exactly the irreversible-effect information an agent needs before a mutation with zero annotation coverage.

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 effect and the destructive consequence before the procedural gate, which is the right ordering. Slightly verbose in places ("This is not an additive act" and the rhetorical gloss on why inventing a season makes the timeline meaningless) but that redundancy is purposeful pressure against a dangerous default.

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 destructive mutation with no annotations and no output schema, the description covers the irreversible effects, the consent protocol, the first-call return behavior, an alternative action when uncertain, and a pointer to umtri://rules/seasons for deeper rules. Nothing an agent needs to call this safely 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%, so the baseline is 3; the description earns above that by explaining what confirm actually does mechanically — omitting it yields the confirmation payload of what would be sealed, while confirm:true applies it. It also frames label's meaning semantically (a human's declaration that a chapter closed), though the schema already covers slug and label examples.

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 ("Creates a new season") plus the immediate side effect that defines the tool: it becomes the "now" season. That side effect alone separates it from list_seasons and from node-creation siblings, which merely attach records to an existing season.

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?

Gives an explicit when-not-to-use rule ("Unsure which season a node belongs to? Attach it to the existing now-season instead of opening a new one") and a precise two-call protocol: first call without confirm to preview, surface that to the user in the agent's own words, then call with confirm:true only after consent. It also forbids the most likely failure mode, passing confirm on the agent's own judgment.

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

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