Skip to main content
Glama

List routines

list_routines
Read-only

List this person's routines in Alexein - briefs, scheduled tasks, alerts and reminders, once or repeating - each with its id, title, status, when it next runs and how its last run went. Use it when they ask what is set up, and before skip_routine to find the id.

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": "list_routines"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered and the description only needs to add scope. It does add useful scope: the listing is implicitly bound to 'this person' despite zero parameters, and it enumerates the shape of each entry. It stops short of explaining how that person is resolved from context or whether results are ever truncated.

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?

Two sentences, front-loaded with the core action before the enumeration, then the usage rule. The field list is dense but each item is informative rather than decorative; nothing is wasted.

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 no parameters, no output schema and read-only annotations, the description carries exactly the load it must: what is listed, what each entry contains, and when to call it. The only unstated detail is how the current person is determined, which is a minor point for a context-bound listing tool.

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 zero parameters, so the established baseline is 4 and there is no parameter semantics to document. The description's mention of implicit person-scoping is the only relevant framing, and no field-level detail is required.

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 (list) and resource (this person's routines), then disambiguates the resource by enumerating the concrete kinds — briefs, scheduled tasks, alerts, reminders, once or repeating. It also names the fields returned (id, title, status, next run, last run outcome), which is essential because there is no output schema.

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 trigger ('when they ask what is set up') and an explicit prerequisite relationship ('before skip_routine to find the id'). The agent knows both when to reach for this tool and why it must precede a specific sibling.

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