Skip to main content
Glama

Score a day of tasks (One-Day Tally)

score_daily_tasks
Read-onlyIdempotent

Scores tasks on four yes-or-no tests (repeats weekly, follows a pattern, 80% draftable, low risk) and picks the one job to start with. Also estimates weekly hours handed back for that job. An estimate, never a promise.

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

Input Schema

NameRequiredDescriptionDefault
tasksYesThe tasks from one normal day.
draft_shareNoShare of the time a draft plausibly hands back. Default 0.6.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent, closed-world and non-destructive behavior, so the description only needs to add semantics. It does add real value: it explains that the score comes from four discrete criteria and states the output is a heuristic estimate, 'never a promise,' which sets correct expectations about precision the annotations cannot express.

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

Conciseness5/5

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

Two sentences, front-loaded with the mechanism (four yes-or-no tests) and closed with the two outputs, followed by a one-line caveat. Nothing is repeated from the schema and no wording is wasted.

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 two-parameter, closed-world, read-only scoring tool this covers what the agent needs to call it and interpret the result. With no output schema, a sentence on how the picked job and hour estimate are returned would close the only remaining gap.

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 description coverage is 100%, with each boolean, name and minutes_per_week documented in the schema itself, so the baseline is 3. The description corroborates the four boolean tests but never mentions draft_share directly and adds no format or syntax detail beyond what the schema already supplies.

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?

Names a specific verb (scores) and resource (tasks from one day), enumerates the four tests the score is built from, and states the two outputs: the one job to start with and estimated weekly hours handed back. That is far more than the title restates and makes the tool's role unmistakable next to setup/skill-oriented siblings.

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

Usage Guidelines3/5

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

Implicit usage is clear from the wording (score a day's tasks to pick where to start), and the schema's 'tasks from one normal day' pins the input context. But there is no explicit when-to-use or when-not statement and no named alternative for the multi-day or setup-wide tools, so the agent must infer selection.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources