Skip to main content
Glama
theluckystrike

mcp-office-suite

by theluckystrike
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Add time entry

entry_add

Log worked time with start and end or minutes, set hourly rate, and receive entry ID, duration, and amount.

Instructions

Log time already worked as one entry and return its id, duration and amount. Give start plus end or minutes. rate is hourly in MAJOR units and is frozen on the entry, so a later rate change never moves it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNoISO 8601 end time (or use minutes)
noteNoOptional note
rateNoHourly rate for this entry; a number (90) or the words the user said ('90 euros an hour')
tagsNoOptional tags
taskNoWhat the work was
startYesISO 8601 start time, e.g. 2026-09-02T09:00:00
minutesNoDuration in minutes (alternative to end)
projectYesProject or client name. A partial name that matches exactly one existing project is used as that project.
billableNoDefault true; set false for non-billable work
currencyNoCurrency of the rate: EUR, USD, GBP, PLN, or words like 'euros'. Defaults to the project currency, else USD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.20.0

TDQS

A3.8/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 discloses a key behavioral detail (rate is frozen on the entry) and the return values, but omits prerequisites, error handling, side effects, or any state changes beyond creation. Partial disclosure only.

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 compact—two sentences with no fluff. It front-loads the purpose and integrates the critical rate behavior efficiently. Slightly dense, but appropriately sized for the tool's complexity.

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?

With 10 parameters, no output schema, and no annotations, the description is thin. It doesn't mention required fields (project, start), the conflict if both end and minutes are provided, default billable behavior, or error handling. It covers the essentials but leaves significant gaps for a tool of this complexity.

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 adds value by clarifying the start+end vs. minutes alternative and explaining that 'rate' is in MAJOR units and frozen, which goes beyond the schema's property descriptions. This is a meaningful addition.

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 action ('Log time') and the resource ('one entry'), and distinguishes from timer tools by specifying 'already worked'. It also lists return values (id, duration, amount), making the purpose unambiguous.

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 phrase 'already worked' implies this is for completed time vs. ongoing timers (timer_start), but it never explicitly names alternatives or conditions for using entry_edit or when not to use this tool. No explicit when-to-use or when-not-to-use guidance 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