Skip to main content
Glama
Sign In

Agent Wikis

by io.github.tonbistudio
OverviewDiscussionsAdmin

List routines

list_routines
Read-onlyIdempotent

List the routines (scheduled jobs) that ship with the specialist agents: each has a schedule, the specialist it comes from, the skills its prompt relies on, and whether it is script only (no agent). readable says whether YOU can load it with your current access. Pass query to filter by keywords. Then read_routine one.

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
queryNoOptional keywords, matched against the name, specialist and skills.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds real value beyond them by listing the fields each result carries (schedule, specialist, skills, script-only flag) and explaining that `readable` reflects the caller's own access level. It says nothing about result volume, ordering, or pagination.

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?

Purpose and result shape are front-loaded in the first sentence, with the access flag and filtering guidance following. No filler, though the fragment 'Then read_routine one.' is terse to the point of reading awkwardly.

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 single optional-parameter list tool with no output schema, the description adequately covers what is returned and what the access flag means. The main omission is guidance on result size or how to page through a large routine catalog.

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 100% and the schema describes `query` as matched against name, specialist and skills. The description only restates 'filter by keywords' without adding syntax, matching rules, or multi-keyword behavior, so it does not exceed the schema baseline.

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 and then defines the resource in domain terms ('routines (scheduled jobs) that ship with the specialist agents'), so an agent knows exactly what a routine is. The closing pointer to read_routine draws the boundary with the sibling that fetches a single item.

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?

Gives a concrete workflow: use this to enumerate, pass `query` to narrow by keyword, then call read_routine on a chosen result. It stops short of naming when NOT to use it (e.g. when already holding a routine name, or vs. the search sibling), so it is clear but not exhaustive.

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

All Agent Wikis 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