Skip to main content
Glama
Sign In

AimYear

by io.github.Yahhi
OverviewDiscussionsAdmin

Set routines

set_routines
DestructiveIdempotent

Replace the list of routines: small steps that repeat on fixed weekdays. From today on, each one appears as a plan item on its days; tick it with edit_plan_item, skip it for one day with delete_plan_item. set_plan keeps them. days are ISO weekdays 1=Mon..7=Sun, default every day. perWeek makes it a weekly count: each tick adds its count (default 1), and once the week reaches perWeek it leaves the plan until Monday. Link it to the goal with leverId. minimum is the small version for a bad day ("read one thread" for "talk to one person"). Pass existing ids to keep them.

Input Schema

NameRequiredDescriptionDefault
routinesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / routines / items / properties / minimum
      Added value: +{
+  "description": "the bad-day version, e.g. \"read one thread\"",
+  "type": "string"
+}
    • addedInput schema / properties / routines / items / properties / perWeek
      Added value: +{
+  "description": "weekly count, e.g. 5 for \"talk to 5 people a week\"",
+  "maximum": 9007199254740991,
+  "minimum": 1,
+  "type": "integer"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already mark the tool as destructive and idempotent; the description adds important behavioral detail about replacement, preserving existing ids, plan-item appearance, and perWeek reset behavior. It makes the destructive semantics concrete: omitted routines are effectively removed unless existing ids are passed.

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?

The description is front-loaded with the core purpose and nearly every clause carries useful meaning. It is dense and could be structured more clearly, but it is not padded or repetitive.

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?

For a destructive, nested-array mutation tool with no output schema, the description covers the important lifecycle and parameter behavior. Minor gaps around some nested fields prevent a perfect score.

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?

Although schema description coverage is reported as 0%, the description explains key semantics for days, perWeek, leverId, minimum, and id retention. It leaves area, projectId, and estimateMin less explained, so it compensates substantially but not completely.

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: "Replace the list of routines," then defines routines as recurring weekday steps. It also distinguishes behavior from related tools by naming edit_plan_item, delete_plan_item, and set_plan.

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?

Explains how routines are acted on after creation and that set_plan keeps them, which gives clear operational context. It does not explicitly state when not to use this tool versus set_plan, so it stops short of full alternative routing.

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

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