Skip to main content
Glama

Check Connection (TimeLog)

timelog_check_connection
Read-onlyIdempotent

Verify that your TimeLog API token works and identify which TimeLog user it belongs to, so you can confirm access rights before reading or writing data.

Instructions

Check that the token works and show which TimeLog user it belongs to. The token has that user's rights.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, so safety is covered; the description adds genuinely useful permission semantics ('the token has that user's rights'), which tells the agent all subsequent calls run with that identity's privileges. However, it does not state what happens when the token is invalid (error vs negative result), which is central behavior for a connectivity check.

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?

Two short sentences with no filler: the action is stated first, the observable result second, and the permission implication last. Nothing is redundant or buried.

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?

No output schema exists, and the description compensates by naming the returned identity; with zero parameters and annotations carrying the safety profile, the only missing piece is failure behavior for an invalid or expired token.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate, and the empty schema plus additionalProperties=false is consistent with a parameterless probe.

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 and resource ('Check that the token works') plus the concrete result ('show which TimeLog user it belongs to'), which clearly separates it from the data-oriented siblings such as timelog_get_employee or timelog_list_projects.

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: an agent can infer this is a pre-flight/auth verification call, but the description never says when to prefer it (e.g., on first call, before write operations, or after an auth failure) or what alternative to use instead.

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