Tripletex MCP Server

search_timesheet_weeks

Search weekly timesheet status in Tripletex by employee ID and week-year to track work hours and manage time reporting.

Instructions

Search weekly timesheet status.

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": "search_timesheet_weeks"
  }
}

Input Schema

Name	Required	Description
`employeeIds`	No	Employee ID(s), comma-separated
`weekYear`	No	ISO week-year (e.g. '2026-07')
`from`	No	Pagination offset
`count`	No	Number of results

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Feb 16, 2026

TDQS

C2.6/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action ('search') without detailing behavioral traits like whether it's read-only, requires authentication, has rate limits, or what the output format might be. For a search tool with zero annotation coverage, this is a significant gap in transparency.

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?

The description is a single, concise sentence with no wasted words. It is front-loaded and efficiently conveys the core action, though it could be more informative. The brevity is appropriate but borders on under-specification.

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?

Given the complexity of a search tool with 4 parameters, no annotations, and no output schema, the description is incomplete. It lacks details on behavioral traits, usage context, and output expectations, making it insufficient for an agent to fully understand how to invoke and interpret results from this tool.

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?

The input schema has 100% description coverage, so the schema already documents all parameters (employeeIds, weekYear, from, count). The description adds no additional meaning beyond what the schema provides, such as explaining parameter interactions or default behaviors. This meets the baseline for high schema coverage.

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 description states the purpose as 'Search weekly timesheet status,' which is clear but vague. It specifies the verb 'search' and resource 'weekly timesheet status,' but lacks specificity about what 'status' entails or how it differs from sibling tools like 'search_timesheet_entries' or 'get_timesheet_month.' This makes it minimally adequate but not distinct.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention any context, prerequisites, or exclusions, such as how it compares to other search or get tools in the sibling list. This leaves the agent without direction on tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.