InstaClock

Time summary

get_summary

Read-onlyIdempotent

Total tracked time for a period, broken down by activity and by day, in the user's timezone. Weeks start on Monday. A running timer counts up to now.

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": {
      "period": "<period>"
    },
    "name": "get_summary"
  }
}

Input Schema

Name	Required	Description
`to`	No	Last day, YYYY-MM-DD. Only for custom.
`from`	No	First day, YYYY-MM-DD. Only for custom.
`period`	Yes	Named period, or "custom" with from and to

Output Schema

Name	Required	Description
`byDay`	Yes	Days with tracked time, in the user's timezone
`range`	Yes	The period as UTC instants; to is exclusive
`period`	Yes
`timezone`	Yes	The user's IANA timezone. Times in this result are in this zone.
`byActivity`	Yes	Most time first
`topActivity`	Yes	null when nothing was tracked
`totalMinutes`	Yes
`includesRunningEntry`	Yes	True when a running timer is counted up to now

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover the read-only/idempotent safety profile, so the description earns credit for the genuinely non-obvious behavior it adds: results are in the user's timezone, weeks are Monday-anchored, and an in-flight timer is counted up to now. It does not discuss limits on period range or cache freshness, but the important semantics are disclosed.

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?

Four short sentences, front-loaded with what the tool returns, followed by the edge-case semantics. No filler or restatement of the title.

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

Completeness5/5

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

With an output schema covering the return shape and annotations covering safety, the description supplies exactly the missing pieces: aggregation granularity, timezone, week boundary, and running-timer behavior. Nothing an agent needs to call this correctly is absent.

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 coverage is 100%, so the schema already documents from/to/period and the enum. The description adds one useful clarification ('weeks start on Monday') that pins down this_week/last_week semantics, but says nothing about how 'custom' interacts with from/to, which is the one ambiguous combination in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('total tracked time for a period') plus the aggregation dimensions (by activity, by day). This clearly differentiates it from entry-level siblings like list_time_entries, though it does not name those siblings explicitly.

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?

Usage is only implied: an agent can infer this is the aggregate view rather than the raw list, but the description never says when to prefer get_summary over get_weekly_review, get_status, or list_time_entries, nor does it state any prerequisites.

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

All InstaClock tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?