toggl-mcp

get_summary

Retrieve total time tracked per project for a specified date range, defaulting to the current week.

Instructions

Get total time tracked per project for a date range. Defaults to the current week.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_summary"
  }
}

Input Schema

Name	Required	Description	Default
`end_date`	No	End date in YYYY-MM-DD format (default: today)
`start_date`	No	Start date in YYYY-MM-DD format (default: start of current week)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 29, 2026

TDQS

A4/5.0

Behavior3/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. It indicates a read-only query ('Get total time') with no side effects, but does not disclose potential rate limits, authentication requirements, or any other behavioral constraints beyond the implied safe operation.

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?

The description is two sentences, front-loaded with the core purpose, and contains no unnecessary words. Every piece of information is relevant and efficiently presented.

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 simple tool with two parameters and no output schema, the description adequately covers the return value (total time per project) and default behaviors. It does not detail the return structure (e.g., list vs. object) but remains complete enough for an agent to invoke correctly.

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?

Both parameters are fully covered by the schema (100% coverage) with clear formats. The description adds context by explaining defaults ('Defaults to the current week') and how the parameters together produce per-project totals, enhancing understanding beyond the raw schema.

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 clearly states the verb ('Get'), resource ('total time tracked per project'), and scope ('for a date range'), effectively distinguishing it from siblings like 'get_recent_entries' (individual entries) and 'get_projects' (project list).

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?

The description implies usage for aggregated time summaries per project, but does not explicitly state when not to use it or name alternative tools for finer-grained data (e.g., 'get_recent_entries'). No exclusions or prerequisites are mentioned.

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

Deploy Server