Skip to main content
Glama
Sign In
@lewinnovation/clockify-mcp-server

@lewinnovation/clockify-mcp-server

by lewinnovation
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_current_user

Retrieve the currently authenticated Clockify user from the API key. Optionally include workspace memberships to verify account identity and access.

Instructions

Returns the currently authenticated Clockify user (from the API key).

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

Input Schema

NameRequiredDescriptionDefault
include_membershipsNoWhen true, include workspace memberships on the user object.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It usefully discloses that the identity is derived from the API key (no user identifier needed), and 'Returns' safely implies a read-only operation, but it says nothing about failure modes (invalid/expired key) or the shape of the returned user.

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?

One sentence, front-loaded with the verb and resource, with the parenthetical clarifying the identity source. Nothing is wasted and nothing needs trimming.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description is the only source for what comes back, and it does say it returns the authenticated user object. It could say more about the returned fields and what include_memberships adds, but for a zero-required-parameter read tool this is nearly sufficient.

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 100% and the single optional parameter 'include_memberships' is fully documented in the schema. The description adds no parameter-level meaning, so the baseline of 3 applies.

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?

States a specific verb ('Returns'), a specific resource ('the currently authenticated Clockify user'), and the source of the identity ('from the API key'). No sibling tool (list_projects, list_workspaces, create_time_entry, etc.) does this, so the agent can distinguish it immediately.

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 implied rather than stated: an agent infers it should call this when it needs the identity behind the configured credentials. There is no explicit when-not guidance and no named alternative, but for a single-purpose identity lookup the implied context is reasonably clear.

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

Deploy Server

Other Tools