Skip to main content
Glama
Sign In
Inserve-MCP

Inserve-MCP

Official
by inserveit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Tijdregistraties bekijken

list_time_registrations
Read-onlyIdempotent

Retrieve time registrations newest first, filtered by operator, ticket, company, or date range, to review logged time and durations in minutes.

Instructions

List time registrations, newest first. Filter on operator, ticket, company and a date range (YYYY-MM-DD). Durations are in minutes.

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

Input Schema

NameRequiredDescriptionDefault
fromNoExecuted on or after this date.
pageNoPaginanummer.
untilNoExecuted on or before this date.
per_pageNoAantal resultaten per pagina (max 100).
ticket_idNoOnly time registered on this ticket.
company_idNoOnly time registered for this company.
operator_idNoOnly time registered by this operator.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: results are ordered newest first, and duration values are expressed in minutes — both of which the agent needs to interpret output. It does not mention pagination defaults or result-size behavior, which the schema only partially covers.

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, front-loaded with the core action, then ordering, then filters, then a units note. Nothing is wasted and no sentence merely repeats the tool name.

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?

For a 7-parameter, all-optional list tool with no output schema, the description covers action, sort order, filter dimensions, date format and duration units — enough to call it correctly. The remaining gap is pagination behavior (defaults, how to walk pages), which the schema documents only at the field level.

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 every parameter (from, until, page, per_page, ticket_id, company_id, operator_id) is already documented, including the YYYY-MM-DD pattern. The description restates the date format and groups the filters by entity, which is mildly helpful orientation but adds no semantics beyond the schema. Baseline 3 applies.

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?

States a specific verb and resource ("List time registrations") plus default ordering ("newest first") and the available filter dimensions. An agent can tell this is the read/list counterpart to the sibling log_time, though the description never names that sibling explicitly.

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 by the word "Filter on...", giving the agent a sense of when the tool applies (querying existing registrations). There are no explicit when-not conditions and no pointer to the sibling log_time for writing time, so the agent must infer the read/write split itself.

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