Skip to main content
Glama

Wakatime Meta

wakatime_meta
Read-onlyIdempotent

Fetch WakaTime API metadata including current server time and available timezones; useful for validating timezone strings before passing them to summaries or durations.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wakatime_meta"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety and network profile is fully covered by structured data. The description adds only that the payload contains server time and timezones; it says nothing about freshness, rate limits, or whether the response is a wrapper around static reference data. An output schema exists, so omitting return formatting is acceptable, leaving modest added value.

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, followed by a compact purpose clause. Nothing is repeated from the schema or annotations and no filler is present.

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 zero-parameter, read-only metadata endpoint with an output schema and full annotation coverage, the description supplies what actually matters: what the payload contains and why an agent would want it. Only marginal gaps remain, such as whether the timezone list is authoritative or cached.

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 of 4 applies. The description correctly implies a no-argument call rather than suggesting any required input.

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+resource ('Fetch WakaTime API metadata') and enumerates the contents ('current server time and available timezones'), which is far more informative than the tautological title 'Wakatime Meta'. It doesn't differentiate itself from the numerous sibling tools (summaries, durations, user, stats), but the resource is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete use case — validating timezone strings — and names the tools that consume those strings ('summaries or durations'), which is genuine routing guidance. It stops short of stating when not to call it (e.g., if you already know the timezone) or that it's a low-cost probe.

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.