Skip to main content
Glama
Sign In
plausible-whenever-mcp

plausible-whenever-mcp

by Schneckenhausmann
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_current_time

Get the current date in a specified site's timezone to ground analytics queries and verify yesterday's date.

Instructions

Get the current date in a site's timezone (today + yesterday as concrete dates). Useful for grounding before analyzing recent data, or to double-check what 'yesterday' resolves to.

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

Input Schema

NameRequiredDescriptionDefault
site_idNoSite domain (e.g. example.com).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, description carries burden. It discloses the output (today, yesterday) and timezone dependency but lacks details on errors, rate limits, or idempotency. For a simple read tool, it's adequate but not comprehensive.

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 sentences: first defines purpose and output, second offers usage guidance. No filler, every sentence earns its place.

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?

Given a single optional parameter, no output schema, and no annotations, the description covers the key aspects: what is returned (today and yesterday), the timezone context, and usage scenarios. Could mention read-only nature or date format, but overall sufficient.

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?

Schema already describes site_id as 'Site domain'. Description adds meaning by connecting the parameter to the timezone context: 'in a site's timezone'. This enriches understanding beyond the schema.

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?

Description clearly states verb 'Get', resource 'current date', and specifies context 'in a site's timezone (today + yesterday as concrete dates)'. This differentiates it from sibling tools like get_stats or get_timeseries, which are analytics-focused.

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?

Provides explicit when-to-use: 'Useful for grounding before analyzing recent data, or to double-check what 'yesterday' resolves to.' No explicit when-not-to-use or alternatives, but the usage context is clear.

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