Skip to main content
Glama
Sign In
solidtime-mcp

solidtime-mcp

by si-essence
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

solidtime_time_entry_delete

DestructiveIdempotent

Delete a Solidtime time entry by ID; deletion is irreversible, so omit confirm for a dry-run preview before executing the write.

Instructions

Delete a time entry. DELETE .../time-entries/{timeEntry}. Irreversible. Omit confirm for a dry-run.

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": {
      "time_entry_id": "<time_entry_id>"
    },
    "name": "solidtime_time_entry_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoSet to the boolean true to execute the write. Omit this field for a dry-run preview. false and the string true are rejected.
time_entry_idYes
organization_idNoOrganization UUID. Falls back to SOLIDTIME_ORGANIZATION_ID, then a single membership from GET /v1/users/me/memberships.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the bar is lower, and the description adds the non-obvious dry-run/preview mechanism that is absent from the annotations. 'Irreversible' reinforces the destructive profile rather than contradicting it. It stops short of describing what a dry-run returns or what permissions are required.

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?

Three short sentences, zero filler, and the destructive nature is surfaced immediately after the purpose. The safety-relevant dry-run instruction is given its own sentence so it is not buried.

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 3-parameter destructive mutation with no output schema, the description covers the essentials: what is destroyed, that it cannot be undone, and how to preview safely. Remaining gaps (dry-run response shape, permission requirements, ID format) are minor but real.

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 67%: confirm and organization_id are well documented in the schema, including the env-var fallback, so the description adds little there. time_entry_id has no schema description, and the description only implies its form via the path template rather than stating the expected UUID format. Baseline 3 fits since the schema does most of the work.

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 and resource ('Delete a time entry') plus the underlying endpoint path, which makes the scope unambiguous against sibling write tools. It does not explicitly contrast with solidtime_time_entries_bulk_delete, but the singular phrasing and {timeEntry} path make single-record scope inferable.

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 line 'Omit confirm for a dry-run' gives a concrete invocation workflow and warns that the operation is irreversible, which is useful. However, there is no guidance on when to prefer this over solidtime_time_entries_bulk_delete, and no stated prerequisites or permission context.

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