Skip to main content
Glama

save_timesheet_draft

Create or edit a draft staff time entry. Use revision 0 for a new entry and the current revision for an edit. Enter local start and end times with the shift time zone.

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": {
      "id": "<id>",
      "revision": "<revision>",
      "staffId": "<staffId>",
      "timeZone": "<timeZone>",
      "start": "<start>",
      "end": "<end>",
      "breakMinutes": "<breakMinutes>",
      "note": "<note>"
    },
    "name": "save_timesheet_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
endYes
noteYes
startYes
staffIdYes
revisionYes
timeZoneYes
breakMinutesYes
endOccurrenceNofirst
startOccurrenceNofirst

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare this is a non-readonly, non-destructive, non-idempotent, closed-world mutation, so the safety profile is covered. The description usefully adds that the result is a *draft* (not a submitted/approved entry) and that revision acts as a concurrency token. It does not disclose what happens on a revision mismatch, whether edits overwrite all fields or merge, or any validation/auth requirements, which is the gap for a write tool with 8 required parameters.

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?

Two tight sentences, front-loaded with verb+resource followed by the invocation rules. No filler or redundancy; the only shortfall is that brevity comes at the cost of leaving required parameters unexplained rather than that the sentences are badly ordered.

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?

Ten parameters, eight required, zero schema descriptions, no output schema, and a 2-sentence description is not enough to invoke this reliably. The most consequential omissions are the meaning of id and staffId, breakMinutes units/limits, and how the two occurrence enums interact with local times across DST — none of which is inferable from the structured fields alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning and it only partially does: it explains revision (0 = new, current = edit) and that start/end are local times paired with timeZone. It says nothing about id, staffId, breakMinutes, note, or the startOccurrence/endOccurrence DST-disambiguation parameters, which are exactly the ones an agent would get wrong without help.

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 pair and resource: 'Create or edit a draft staff time entry.' An agent can tell this is the draft-persistence tool rather than the workflow tools like submit_timesheet or approve_timesheet. It stops short of naming any sibling explicitly, so it does not fully disambiguate from sibling save_* draft tools.

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 revision rule ('use revision 0 for a new entry and the current revision for an edit') tells the caller how to invoke it for both modes, which is real guidance. However, it gives no when-to-use context versus alternatives such as submit_timesheet or a dedicated create path, and no prerequisites (permissions, whether the staff member must exist, what to do on a stale revision).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources