Skip to main content
Glama

Rank tasks + build a daily plan (deterministic)

rank_day

Compute a deterministic priority-ranked, time-block-aware daily plan from supplied tasks and calendar events, scoring importance and urgency to place work into available slots.

Instructions

Compute a priority-ranked, time-block-aware daily plan from tasks + calendar events you supply. Gather the inputs FIRST via the other tools, then pass them here: tasks from Todoist (find-tasks / find-tasks-by-date) — pass each task's raw fields incl. priority (Todoist API: 4=P1 highest … 1=P4), due, deadline, duration; events from the calendar (list-events) and optional busy intervals from get-freebusy; and now/timezone from get-current-time. This returns the DETERMINISTIC ranking + plan (weighted importance×urgency score + Eisenhower label, duration-aware placement). It does NOT apply your PRIORITIES.md/GOALS.md policy — read those (read_priorities/read_goals) and apply them yourself as a tie-breaker/override on the returned ranking before presenting the plan.

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": {
      "tasks": "<tasks>",
      "events": "<events>",
      "now": "<now>",
      "timezone": "<timezone>"
    },
    "name": "rank_day"
  }
}

Input Schema

NameRequiredDescriptionDefault
nowYesCurrent instant (RFC3339), e.g. from get-current-time.
busyNoOptional busy intervals (e.g. from get-freebusy), ISO 8601.
tasksYesTodoist tasks to rank.
eventsYesFixed calendar events for the day.
timezoneYesIANA timezone, e.g. America/New_York.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that ranking is deterministic, names the scoring model (weighted importance×urgency, Eisenhower label, duration-aware placement), and explicitly delimits the one behavioral surprise (no policy application, agent must override). It stops short of stating that the call is side-effect free/stateless or describing failure behavior on malformed inputs.

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 the tool does, then the input-gathering instructions, then the scope caveat — a sensible order. The dense parentheticals (tool names, field lists, priority mapping) are informative but make the middle sentence heavy; only mild trimming would be possible without losing guidance.

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 compute-heavy tool with five parameters and no output schema, the description covers input preparation, the scoring model, and the policy boundary. The remaining gap is return structure: with no output schema, it says only 'ranking + plan (score + Eisenhower label)' and does not describe the shape of the returned plan blocks, which would help an agent consume the result without guessing.

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 baseline is 3; the description earns a notch above by adding provenance and selection guidance — which task fields matter (`priority`, `due`, `deadline`, `duration`), the Todoist priority encoding (4=P1 highest … 1=P4), and that `busy` is optional. It adds usable meaning around where each parameter comes from rather than restating schema text.

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+resource: 'Compute a priority-ranked, time-block-aware daily plan from tasks + calendar events'. The '(deterministic)' qualifier and the explicit note that it does NOT apply PRIORITIES.md/GOALS.md policy separate it cleanly from policy-aware siblings like reconcile_and_rank and project_day.

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 ordering rule ('Gather the inputs FIRST via the other tools, then pass them here') and names the exact source tools: find-tasks / find-tasks-by-date for tasks, list-events for events, get-freebusy for optional busy, get-current-time for now/timezone. It also states the boundary condition — read_priorities/read_goals must be applied by the agent afterwards as a tie-breaker — so the agent knows both when to call it and what to do next.

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