Skip to main content
Glama
Sign In
solidtime-mcp

solidtime-mcp

by si-essence
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

solidtime_time_entries_bulk_delete

DestructiveIdempotent

Bulk delete up to 500 time entries irreversibly; omit confirm to preview a dry run, then set confirm true to execute.

Instructions

Delete many time entries. DELETE .../time-entries?ids[]. 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": {
      "ids": "<ids>"
    },
    "name": "solidtime_time_entries_bulk_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes
confirmNoSet to the boolean true to execute the write. Omit this field for a dry-run preview. false and the string true are rejected.
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

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is known. The description still adds useful context the annotations do not carry: that the deletion is irreversible and that omitting confirm yields a dry-run preview, plus the underlying endpoint shape.

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, front-loaded with the action and followed by the endpoint, the risk, and the safety mechanism. Nothing is redundant and no sentence could be removed without losing information.

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 destructive bulk operation, the description covers reversibility and the dry-run escape hatch, which are the critical facts. Minor gaps remain: the maximum of 500 ids, all-or-nothing vs partial failure behavior, and batch atomicity are not addressed.

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% and the confirm parameter already documents the dry-run behavior verbatim in the schema. The description restates that behavior rather than adding new semantics, and it never mentions the 1-500 item bound on ids or the organization_id fallback.

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 many time entries") and the word "many" implicitly separates it from the single-entry delete sibling. It stops short of naming solidtime_time_entry_delete or solidtime_time_entries_bulk_update explicitly, so the differentiation is only partial.

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?

Gives actionable usage context by describing the confirm/dry-run workflow, which tells the agent how to safely preview before committing. It does not state when to prefer single-entry deletion or bulk_update over this tool, so no explicit alternatives are offered.

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