Skip to main content
Glama
Sign In
rocketmatter-mcp

rocketmatter-mcp

by RosenAdvertising
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

delete_time_entry

Delete a time entry by providing its unique ID to remove incorrect or unwanted time records.

Instructions

Delete a time entry by ID (GUID).

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": "delete_time_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
time_entry_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It only says 'Delete', implying a destructive action, but does not disclose side effects, permanence, or required permissions. The agent has minimal information about the tool's behavior beyond the name.

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 sentence with no redundancy. It is front-loaded with the action and resource, and every word earns its place.

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?

Given the tool's simplicity (one parameter, output schema exists) and the absence of annotations, the description is minimally adequate. It covers the basic purpose but lacks details on behavioral traits like irreversibility, which could be important for a delete operation.

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?

The schema has 0% description coverage, but the description adds the key semantic detail that the ID is a GUID, which is not in the schema. This provides meaningful guidance on the parameter format.

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 verb 'Delete' and the resource 'time entry', and specifies the method 'by ID (GUID)', which distinguishes it from siblings like create_time_entry, update_time_entry, and get_time_entry.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives, prerequisites, or whether the deletion is irreversible. The description only states what the tool does, not when it should be used.

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