Skip to main content
Glama

Get routines

get_routines
Read-onlyIdempotent

Read ALL of the user's Habidu routines - the built-in morning and evening routines (routineKey morning/evening) and their own - sorted by start time, each with id, title, time, duration, repeat days, per-weekday times, ordered steps and enabled (false = switched off or archived). Use it before update_routine or delete_routine for the ids and current steps. Today's single occurrences are also in get_tasks. No routines returns count 0. Read-only, takes no parameters.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_routines"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered structurally. The description adds genuinely new behavior: results are sorted by start time, the 'enabled' flag being false means switched off or archived, and an empty result returns count 0.

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 tool's purpose and return fields are front-loaded in the first sentence, with routing guidance following. It is dense but nearly every clause carries information; the long parenthetical field list is the only mildly heavy element.

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?

With zero parameters and no output schema, the description carries the full burden of describing returns, and it does so: field list, ordering, enabled/archived semantics, and the empty-result case. Nothing an agent needs to call and interpret this tool 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?

The tool takes no parameters, so the baseline is 4. The description correctly states 'takes no parameters', consistent with the empty schema, though it adds nothing further because there is nothing to explain.

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?

The description names a specific verb and resource (read ALL of the user's routines), enumerates what is included (built-in morning/evening plus the user's own), and states the sort order. It also distinguishes itself from get_tasks by noting that today's single occurrences live there.

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?

It gives an explicit precondition: 'Use it before update_routine or delete_routine for the ids and current steps', and routes today's individual occurrences to get_tasks. Both when-to-use and the relevant alternative are stated rather than inferred.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources