Skip to main content
Glama
Sign In
SyncroMSP MCP Server

SyncroMSP MCP Server

by advenimus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

time_list_timelogs

Retrieve employee time logs from SyncroMSP. Filter by user ID and page through clock in/out records.

Instructions

List employee time logs (clock in/out records)

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number
user_idNoFilter by user ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description fails to disclose behavioral traits like pagination behavior, rate limits, or what constitutes a time log entry. The brief description provides no insights beyond the basic purpose.

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?

Single sentence is efficient and front-loaded. However, it could include more contextual details without sacrificing conciseness, especially given the lack of guidance.

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?

No output schema means the description should explain what the list returns (e.g., fields, pagination info). It does not, leaving the agent uncertain about the response format. Given moderate complexity, this is inadequate.

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%, so the baseline is 3. The description adds no additional meaning beyond the schema's parameter descriptions, which already explain user_id and page.

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?

Description clearly states 'List employee time logs (clock in/out records)', providing a specific verb+resource. It distinguishes from sibling tools like time_list_timers by mentioning 'time logs' versus 'timers'. The parenthetical clarifies the type of logs.

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 on when to use this tool versus alternatives such as time_list_timers or time_get_last_timelog. Lacks context for filtering by user or pagination, leaving the agent to infer usage.

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