Skip to main content
Glama
saaqibz

toggl-mcp

by saaqibz

create_time_entry

Log a time entry into Toggl Track using start/end times in Eastern Time, a description, and a tag. Automatically converts times to UTC.

Instructions

Logs a new time entry into Toggl.
LLM Notes:
- Always use the get_tags tool first to find a matching existing tag before calling this tool.
- Always check with get_entry_descriptions tool to see if there's a very similar description that exists and use that as the description.

@param start_time the start datetime in ET (New York) e.g., "2026-03-07T07:30:00"
@param end_time the end datetime in ET (New York) e.g., "2026-03-07T07:30:00"
@param description the activity performed e.g., "Walked dog"
@param tag the tag associated with the entry e.g., "chore"
@returns a time entry object. Make sure to review it for what was actually added.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagYes
end_timeYes
start_timeYes
descriptionYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior3/5

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It adds value by specifying the ET timezone for start_time/end_time and by instructing the agent to review the returned time entry for what was actually added, hinting at possible modifications. However, it does not mention potential validation errors, permission requirements, or constraints like overlapping entries, leaving some behavioral aspects opaque.

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 efficiently structured: a one-sentence purpose statement, two essential LLM Notes, and clear parameter/return documentation. Each section earns its place with no redundant or filler content.

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?

For a create tool with an output schema, the description covers all necessary context: purpose, prerequisite steps (tag and description lookups), timezone expectations, parameter meanings, and a note to review the returned object. It is complete and actionable for the agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema provides zero descriptions and only property names (tag, end_time, start_time, description). The description compensates fully by documenting each parameter with a human-readable explanation and a concrete example, including the timezone format. This adds substantial meaning 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 begins with 'Logs a new time entry into Toggl,' which is a specific action (create) targeting a clear resource (time entry into Toggl). This clearly distinguishes it from sibling tools like get_tags and get_entry_descriptions, which are read-oriented.

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

Usage Guidelines5/5

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

The LLM Notes explicitly instruct the agent to always call get_tags first and to check get_entry_descriptions for similar descriptions before using this tool. This provides concrete when-to-use guidance and names the alternative tools to consult first, going beyond generic context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/saaqibz/toggl-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server