Skip to main content
Glama

load-routines

Load and execute pre-configured routines by stitching together actions from MCP tools, enabling efficient automation and custom workflows on the fly.

Instructions

Load routines

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:57-73 (registration)
    Registration of the 'load-routines' MCP tool, including empty input schema, description, and inline handler function.
    server.tool(
      "load-routines",
      "Load routines",
      {},
      async () => {
        const routines = await loadRoutines(routineFilename)
    
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(routines, null, 2)
            }
          ]
        }
      }
    )
  • The handler function for the 'load-routines' tool. It loads the routines from the JSON file using the imported loadRoutines function and returns them formatted as a JSON string in the tool response.
    async () => {
      const routines = await loadRoutines(routineFilename)
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(routines, null, 2)
          }
        ]
      }
    }
  • Input schema for the 'load-routines' tool, which accepts no parameters (empty object).
    {},
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Load routines' gives no insight into what the tool does behaviorally—whether it's a read-only operation, requires authentication, has side effects, or handles errors. It fails to describe any behavioral traits, leaving the agent with no understanding of how the tool behaves beyond its vague name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is overly concise to the point of under-specification. 'Load routines' is a two-word phrase that lacks necessary detail for effective tool use. While it avoids verbosity, it fails to provide essential information, making it inefficient rather than appropriately concise. Every word should earn its place, but here the description is too sparse to be useful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is incomplete for a tool that likely performs a data retrieval operation. It doesn't explain what 'load' entails (e.g., returns a list, fetches details), how results are structured, or any operational context. With no structured fields to compensate, the description fails to provide the necessary completeness for an agent to use the tool effectively.

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 input schema has 0 parameters with 100% description coverage, meaning no parameters need documentation. The description doesn't add parameter details, which is acceptable given the absence of parameters. Since there are no parameters to explain, the description adequately avoids unnecessary complexity, aligning with the schema's completeness.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Load routines' is a tautology that essentially restates the tool name without adding meaningful context. While it indicates the action ('load') and resource ('routines'), it lacks specificity about what 'load' means in this context (e.g., retrieve, fetch, list) and doesn't distinguish it from sibling tools like 'create-routine' or 'update-routine'. This minimal description provides only basic purpose without clarity on scope or differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, context for usage, or comparison with sibling tools such as 'create-routine', 'delete-routine', or 'update-routine'. Without any usage instructions, an agent cannot determine appropriate scenarios for invoking this tool over others.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mquan/routine'

If you have feedback or need assistance with the MCP directory API, please join our Discord server