Skip to main content
Glama

get_timesheet

Read-onlyIdempotent

Read a staff time entry and its current revision 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"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds two useful pieces beyond that: the response includes the 'current revision' (versioning context) and results are bounded to the approved business (tenant scoping). It says nothing about permission requirements or what happens for a non-existent or unapproved-business id.

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?

One short sentence with no filler, and the core action is front-loaded. The trailing phrase 'in the approved business' is slightly opaque phrasing, but it carries real scoping information rather than padding.

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?

The description hints at the return shape ('entry and its current revision') which partially compensates for the absent output schema, and annotations carry the safety profile. However, for a fetch tool whose only input is completely undocumented, the definition leaves the agent without enough to know what id to supply or what the revision field means.

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?

There is one required parameter with 0% schema description coverage — the schema only supplies a uuid format and pattern, with no indication of what the id identifies. The description does not disambiguate whether it is a timesheet id, a staff id, or an appointment id, so the single most important calling detail is left to guesswork.

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 gives a specific verb ('Read') and a specific resource ('a staff time entry and its current revision'), scoped to 'the approved business'. An agent can tell this is a single-record fetch. It stops short of distinguishing itself from the close sibling get_timesheet_history, which it never mentions.

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: fetch one time entry by identifier. There is no statement of when to prefer this over get_timesheet_history or the other timesheet siblings, and no preconditions or exclusions are given.

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