Skip to main content
Glama

early_edit_tracking

Idempotent

Edit the current time tracking entry by updating its note, activity, or start time. Use it to correct or adjust an active tracking session through the Early time tracking API.

Instructions

Edit the current tracking (note, activity, start 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": {
      "params": "<params>"
    },
    "name": "early_edit_tracking"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

The annotations already declare that this is a non-read-only, idempotent, non-destructive mutation, so the description carries a lower burden. However, it adds no behavioral context beyond restating the editable fields, such as what happens if no tracking is active, whether omitted fields remain unchanged, or what authorization is required.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is a single compact sentence with the core action and editable fields front-loaded. There is no wasted wording, though the brevity leaves important behavior unstated rather than making the sentence itself inefficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool, the description is incomplete: it does not explain that a current tracking session is required, does not clarify partial-update behavior, and does not mention any failure conditions. The presence of an output schema means return values need not be described, but the missing operational context is a substantial gap.

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 description names the three editable fields—note, activity, and start time—which maps to the nested parameters in the input object. With schema description coverage reported as 0%, the description should compensate more, but it adds little detail beyond field names; the schema itself contains richer descriptions for tags, mentions, and ISO 8601 start-time syntax.

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?

The description uses a specific verb and resource: 'Edit the current tracking,' and names the editable fields note, activity, and start time. This clearly distinguishes it from generic tracking actions, but it does not explicitly differentiate it from nearby edit siblings such as early_edit_time_entry or early_edit_activity.

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?

The description provides no explicit guidance on when to use this tool, what prerequisites must hold, or which alternatives to consider. It implies the user must have a current tracking session, but never states that condition or explains when another edit tool would be more appropriate.

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