Skip to main content
Glama
Sign In
timedoctor-mcp

timedoctor-mcp

by frifster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_hours_summary

Retrieve a summary of hours worked by project for any date. Input a date to see time allocation across projects.

Instructions

Get a quick breakdown of hours by project for a specific date

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

Input Schema

NameRequiredDescriptionDefault
dateYesDate in YYYY-MM-DD format (e.g., 2025-01-15). Use 'today' for current date.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description must fully convey behavioral traits. It only mentions a 'quick breakdown' but does not state whether the operation is read-only, requires authentication, or any other behavioral details (e.g., what happens if date is invalid, rate limits). The description lacks transparency.

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?

The description is a single sentence that is front-loaded with the core purpose. It is concise and to the point, but could be slightly expanded to include usage guidance without becoming verbose. Still, it is effective for a simple tool.

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

Completeness3/5

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

Given the tool's simplicity (single parameter, no output schema), the description covers the basic purpose. However, it does not mention the output format or any aggregation details, and lacks context on when to prefer this over sibling tools. Adequate but incomplete.

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% and the input schema already describes the date parameter format and the 'today' option. The description adds no additional meaning beyond 'specific date', so it provides no extra value over the schema. Baseline of 3 is appropriate.

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?

The description states 'Get a quick breakdown of hours by project for a specific date', which clearly specifies the verb (Get), resource (breakdown of hours by project), and scope (for a specific date). This distinguishes it from sibling tools like export_today_csv or get_daily_report, which serve different purposes.

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 does not provide any guidance on when to use this tool versus alternatives (e.g., get_daily_report, export_today_csv). No when-to-use, when-not-to-use, or prerequisite information is given.

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

Deploy Server

Other Tools