Skip to main content
Glama
Sign In

Agent Wikis

by io.github.tonbistudio
OverviewDiscussionsAdmin

Read a routine

read_routine
Read-onlyIdempotent

Load one routine by name: the schedule, the agent prompt, and the list of scripts and settings it needs. Add path to read one listed file (e.g. "scripts/ad_report.py"). Nothing runs here: the routine is set up and run on the user's machine. Before saving, running or scheduling anything from it, show the user what it does and get their explicit OK. Never create the scheduled job without the user's confirmation. Each file comes with its sha256. Needs a Pro key; without one you get how to unlock it.

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": {
      "name": "<name>"
    },
    "name": "read_routine"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesRoutine name from list_routines, e.g. "daily-ad-report".
pathNoOptional file within the routine, as listed by read_routine.
specialistNoOnly needed if two specialists ship a routine with the same name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: it discloses that nothing executes remotely, that setup and execution happen on the user's machine, that a Pro key is required with an unlock path on failure, and that returned files carry sha256 hashes. The confirmation-before-scheduling constraint is a behavioral trait no annotation conveys.

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-loads what is loaded and what the path parameter does, then covers safety and prerequisites. Slightly sprawling because it blends safety policy with the tool's mechanics, but every sentence carries usable information for an agent.

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?

No output schema exists, so the description must describe returns, and it does: schedule, agent prompt, scripts, settings, and per-file sha256. Combined with the Pro-key failure mode and the no-execution caveat, an agent has everything needed to call it correctly and interpret results.

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, but the description adds mode-switching semantics the schema does not: supplying `path` converts the call into a single-file read of an item listed by this same tool. `specialist` disambiguation is left entirely to the schema, which is acceptable given its coverage.

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 ('Load one routine by name') and enumerates the payload: the schedule, the agent prompt, and the list of scripts and settings. It also distinguishes single-item reading from listing via 'one routine by name' and explains the path-driven file mode, so an agent can tell it apart from list_routines without opening a schema.

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 concrete conditional usage: add `path` to read one listed file, with an example. It also supplies a downstream workflow rule (show the user and get explicit OK before saving, running, or scheduling) and rules out expecting execution. It stops short of naming list_routines as the discovery step in the description itself, leaving that to the schema.

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