Skip to main content
Glama

get_timesheet_history

Read-onlyIdempotent

Read the recorded changes to a staff time entry in the approved business.

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

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds the useful framing that the payload is recorded change history scoped to a business, but says nothing about completeness of the history, ordering, retention, or volume/pagination for an entry with many revisions.

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?

A single sentence with the resource and scope front-loaded and no redundant restatement of the tool name. The trailing phrase 'in the approved business' is vague jargon that costs a little clarity without adding actionable meaning.

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 read tool with one required UUID, the description leaves the central question unanswered: what a returned 'recorded change' contains (before/after values, actor, timestamp, status transitions). With no output schema, the description is the only place this could be conveyed, and it is not.

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 coverage is 0%, so the description must carry the load, and it does the most important part: it clarifies that the single 'id' refers to a staff time entry (not a staff member or business). It does not clarify whether the UUID must be a currently approved entry or whether history exists for drafts, leaving edge-case semantics ambiguous.

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 verb+resource pairing ('Read the recorded changes to a staff time entry') is specific and tells an agent this returns an audit/change log rather than the timesheet itself, which separates it from get_timesheet. It stops short of naming that sibling explicitly, so the differentiation must be inferred from the word 'changes'.

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?

Usage is only implied: an agent can infer this is the tool for inspecting what changed on a time entry, but there is no explicit when-to-use, no statement of when to prefer get_timesheet vs this history view, and no prerequisites. Nothing is misleading, but nothing routes the agent either.

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