Skip to main content
Glama
routineco

Routine

Official
by routineco

taskUnplanned

Track and manage unplanned tasks within Routine, ensuring efficient organization and prioritization of unexpected or ad-hoc activities.

Instructions

Unplanned tasks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'taskUnplanned' tool, which retrieves unplanned tasks by making an RPC request to 'task.unplanned' and returns the JSON-formatted data or an error message.
    server.tool("taskUnplanned", "Unplanned tasks.", {}, async ({}) => {
      try {
        const data = await sendRpcRequest("task.unplanned", []);
        return {
          content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
        };
      } catch (error) {
        logger.error("Error fetching task.unplanned: %o", error);
        return {
          content: [
            {
              type: "text",
              text: `Error fetching auth id: ${error instanceof Error ? error.message : String(error)}`,
            },
          ],
          isError: true,
        };
      }
    });
  • src/tools.ts:888-906 (registration)
    Registers the 'taskUnplanned' tool with the MCP server using server.tool(), including name, description, empty schema, and inline handler.
    server.tool("taskUnplanned", "Unplanned tasks.", {}, async ({}) => {
      try {
        const data = await sendRpcRequest("task.unplanned", []);
        return {
          content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
        };
      } catch (error) {
        logger.error("Error fetching task.unplanned: %o", error);
        return {
          content: [
            {
              type: "text",
              text: `Error fetching auth id: ${error instanceof Error ? error.message : String(error)}`,
            },
          ],
          isError: true,
        };
      }
    });
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Unplanned tasks' implies a read operation (likely listing or retrieving), but doesn't confirm if it's safe, destructive, or requires authentication. It doesn't describe return format, error conditions, or any behavioral traits like pagination or rate limits. The description adds minimal value beyond the name.

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

Conciseness3/5

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

The description is extremely concise ('Unplanned tasks.') but this brevity comes at the cost of under-specification. While there's no wasted text, the single phrase fails to provide necessary context about the tool's function. It's front-loaded but insufficiently informative.

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

Completeness2/5

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

Given the tool's apparent simplicity (0 parameters, no output schema), the description is incomplete. It doesn't explain what the tool actually does operationally, what 'unplanned' means contextually, or what users can expect as output. With no annotations and minimal description, an agent would struggle to understand when and how to invoke this 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 tool has 0 parameters with 100% schema description coverage, so the schema fully documents the absence of inputs. The description doesn't need to compensate for parameter documentation gaps. While it doesn't add any parameter-specific information (which isn't needed), it maintains the baseline appropriate for a parameterless tool.

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 'Unplanned tasks' is a tautology that essentially restates the tool name 'taskUnplanned'. It doesn't specify what action the tool performs (list? create? modify?) or what resource it operates on beyond the vague 'tasks'. While it distinguishes from some siblings like 'taskComplete' or 'taskCreateSimple', it doesn't clearly differentiate from 'taskDay' or 'taskUpcoming' which might also relate to task organization.

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

Usage Guidelines2/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. Given siblings like 'taskDay', 'taskGet', 'taskUpcoming', and 'taskUpdate', there's no indication whether this tool is for retrieving, creating, or managing unplanned tasks specifically. No context about prerequisites, timing, or workflow integration is mentioned.

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/routineco/mcp-server'

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