Skip to main content
Glama
Sign In
dVersum MCP Server

dVersum MCP Server

Official
by dversum
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

create_time_entry

Record time worked on a project by entering start and end times, with optional task, billable, and description.

Instructions

Log a completed time entry with start and end time.

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": {
      "project_id": "<project_id>",
      "start_time": "<start_time>",
      "end_time": "<end_time>"
    },
    "name": "create_time_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idNoTask UUID (optional)
billableNoWhether this time is billable (default true)
end_timeYesEnd time in ISO 8601 format
project_idYesProject UUID
start_timeYesStart time in ISO 8601 format
descriptionNoWhat was worked on

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.7/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden. It only states the action without disclosing side effects, return values, permissions, or validation behavior. For a create operation, this is a notable gap.

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 a single, front-loaded sentence with no filler, earning its place efficiently.

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?

For a simple create tool with a fully described schema, this is minimally viable. It lacks guidance on usage context relative to similar tools and does not describe output, but this is acceptable given the straightforward operation.

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?

The input schema has 100% description coverage for all 6 parameters, so the description adds no additional parameter meaning. The baseline of 3 applies because the schema handles parameter documentation.

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 uses the specific verb 'Log' with the resource 'time entry' and mentions start and end time, clearly distinguishing it from timer-management tools like start_timer and stop_timer.

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

Usage Guidelines4/5

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

The word 'completed' implies this is for logging finished work as opposed to tracking in-progress timers, providing clear context. However, there is no explicit reference to alternatives or when-not-to-use conditions.

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