Skip to main content
Glama

Get the timer

get_timer
Read-onlyIdempotent

The running or paused timer of the member of this token, or timer: null.

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_timer"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
timerYesThe timer of the member of the token, or `null`
time_entryNo`billable`, `currency`, `hourly_rate`, `amount`, `invoice_id` and `invoice_number` are only for a role that sees amounts, and `cost_rate`, `cost_currency` and `cost` only for a role that sees costs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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, non-destructive and closed-world, so the safety profile is carried. The description adds genuinely new behavior: the result is limited to the token's own member (no cross-member reads) and the absent-timer case yields `timer: null`, which prevents an agent from treating an empty response as an error.

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?

One short, front-loaded clause with no filler, and the null-case detail is appended rather than buried. It is a sentence fragment rather than a full description, which makes it slightly terse but costs nothing in efficiency.

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?

An output schema exists, so the description needn't detail the return payload, and with no inputs the tool is simple. The essential missing piece for an agent is authorization context — that the token determines which member's timer is returned — which is only gestured at by 'member of this 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 there is nothing for the description to disambiguate; the baseline for a parameterless schema applies. The sentence adds context about response scoping without needing to explain any inputs.

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?

The description names the resource precisely (the running or paused timer) and scopes it to the token's member, which cleanly separates it from timer-mutation siblings such as start_timer, pause_timer and stop_timer. It reads as a return-value fragment rather than an explicit verb+resource statement, so it is clear but not maximally explicit.

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 the read-only way to check current timer state, since all other timer siblings mutate it. There is no explicit statement of when to call it, no mention of prerequisites (e.g. authentication via token) and no named alternative to compare against.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources