Karbon MCP Server

Get timesheet

get_timesheet

Retrieve a specific timesheet using its TimesheetKey, with an option to include individual time entries.

Instructions

Get a single timesheet by TimesheetKey, optionally expanding TimeEntries.

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": {
      "timesheetKey": "<timesheetKey>"
    },
    "name": "get_timesheet"
  }
}

Input Schema

Name	Required	Description	Default
`timesheetKey`	Yes	The Karbon TimesheetKey
`expandTimeEntries`	No	Include individual time entries

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 15, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states that the tool retrieves a timesheet and optionally expands entries. It does not disclose any behavioral aspects such as read-only nature, permissions, error conditions, or side effects. This is insufficient for a mutation-free tool.

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

Conciseness5/5

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

The description is a single sentence that efficiently captures the tool's purpose and optional parameter. It is front-loaded with the key action and resource, with no wasted words.

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 simple tool with 2 parameters and no output schema, the description is minimal but covers the core functionality. However, it lacks any description of the return value format or additional context like error handling, making it barely adequate for an agent to fully understand the tool's behavior.

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 100% with descriptions for both parameters. The description adds minimal value by rephrasing 'by TimesheetKey' and 'optionally expanding TimeEntries,' but it does not provide any additional meaning or syntax beyond the schema. Baseline 3 is appropriate.

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

Purpose5/5

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

The description clearly states the tool gets a single timesheet by its key, with an optional expansion. The verb 'Get' and resource 'timesheet' are specific. It distinguishes from sibling tools like list_timesheets (which lists multiple) and other get tools.

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?

The description implies usage when you have a TimesheetKey and want one timesheet, but it does not explicitly state when not to use it or mention alternatives like list_timesheets for multiple timesheets or list_time_entries for entries alone. No guidance is provided beyond the basic purpose.

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

Deploy Server