Skip to main content
Glama

timesheet

Read-only

Track weekly hours by day and project, flag gaps for review, and generate per-person or team views using member, workspace, and hours-per-day inputs.

Instructions

Hours of a week by day and project; gaps marked

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "timesheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
weekNoA date in it; default now
memberNo
everyoneNoRow per person
workspaceNo
hoursPerDayNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv4.1.1

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The only behavioral detail added is 'gaps marked', which hints that missing entries are surfaced in the result, but with no output schema the description leaves the result shape, default week behavior, and the member/everyone interaction unexplained.

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

Conciseness3/5

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

It is short and front-loaded with no filler, which is good, but the telegraphic semicolon-fragment style makes it clipped to the point of ambiguity rather than efficient. Fewer than ten words is arguably too few for a five-parameter tool.

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?

Five optional parameters, 40% schema coverage, and no output schema mean the description should carry substantial weight, but it explains almost nothing about scope, defaults, or result shape. An agent could call it, but could easily misuse member/workspace/hoursPerDay.

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 coverage is only 40% — week and everyone are described, while member, workspace, and hoursPerDay are bare. The description mentions neither these parameters nor their relationships (e.g., whether member and everyone are mutually exclusive, or what hoursPerDay controls), so it fails to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The phrase 'Hours of a week by day and project' does convey the resource (a weekly timesheet) and its granularity (per day, per project), plus that gaps are flagged. However, it is a noun fragment with no verb, so it never states plainly that it retrieves/reports data, and nothing distinguishes it from adjacent read tools.

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?

There is no when-to-use guidance at all: no mention of when a weekly timesheet view is preferable to other retrieval tools, no prerequisites, and no note on how member vs everyone scoping should be chosen. The agent must infer the use case entirely from the noun phrase.

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