Skip to main content
Glama

submit_timesheet

Submit a draft staff time entry for owner approval. Supply the draft revision you reviewed.

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>"
    },
    "name": "submit_timesheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the description is free to add the state transition (draft to owner approval) and the concurrency precondition of passing the revision you reviewed. It stops short of saying what happens to an already-submitted entry or on a stale revision.

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?

Two short sentences, front-loaded with the action and intent, followed by the one precondition that matters. No filler or restatement of the tool name.

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?

For a two-parameter non-idempotent mutation with no output schema, it covers the action and one precondition but omits what the caller gets back and how stale-revision or already-submitted cases fail. Adequate to attempt the call, thin for handling the result.

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 description coverage is 0%, so the description carries the burden: 'the draft revision you reviewed' gives real meaning to the opaque integer 'revision' as an optimistic-concurrency token. The required 'id' is only implicitly identified as the time entry identifier, and no mismatch or stale-revision consequences are described.

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 ('Submit a draft staff time entry') plus the outcome ('for owner approval'), which separates it in spirit from save_timesheet_draft and approve_timesheet. It never names those siblings, so an agent must infer the boundary from the words alone.

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?

'Submit a draft ... for owner approval' and 'the draft revision you reviewed' imply the precondition that a draft was previously read and reviewed, which is useful. There is no explicit statement of when to prefer this over save_timesheet_draft, approve_timesheet, or return_timesheet, and no exclusions.

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