Skip to main content
Glama

list_timesheets

Read-onlyIdempotent

Read staff time entries and payroll export summaries for the approved business. Supply an inclusive work-date range as YYYY-MM-DD.

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "list_timesheets"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
fromYes

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds two useful behavioral facts beyond that: results are tenant-scoped to 'the approved business' and the date range boundary is inclusive. It does not mention pagination, result caps, date-range limits, or timezone handling for work dates.

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 with zero filler; the resource scope comes first and the parameter instruction second. 'For the approved business' is slightly vague but earns its place as scoping information.

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 read tool with no output schema, the description covers purpose, scope and range semantics. It is missing operational detail an agent would want before calling: whether very wide ranges are allowed, how results are ordered or paged, and what fields the payroll export summary contains.

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 must carry parameter meaning. It does supply the format (YYYY-MM-DD) and, importantly, the inclusive boundary semantics, which the schema's regex cannot express. It says nothing about ordering (from <= to), maximum span, or whether work-date is interpreted in business-local time.

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 ('Read') and specific resources ('staff time entries and payroll export summaries') scoped to 'the approved business'. An agent immediately knows what this returns. It does not name any sibling to contrast against, but no sibling in the list covers timesheets, so differentiation is implicit.

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?

The only guidance is a parameter instruction ('Supply an inclusive work-date range'), which is about how to call it, not when to call it. There is no statement of when this tool is appropriate versus alternatives, no prerequisite or permission conditions, 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