Skip to main content
Glama

Timestamp

by io.github.pipeworx-io

Now

now
Read-onlyIdempotent

The current UTC time as ISO-8601 and Unix timestamp (seconds + milliseconds).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {}
+]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already indicate readOnly, idempotent, non-destructive behavior. Description adds valuable detail about output formats (ISO-8601, Unix timestamps). No contradictions.

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?

Single sentence with all essential information, no unnecessary words. Extremely concise and front-loaded.

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?

No output schema, but description adequately explains return values (ISO-8601 and Unix timestamps). Minor gap: exact structure not specified, but acceptable for a simple tool.

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?

No parameters. Schema coverage 100% is trivially true. Baseline for 0 parameters is 4; description adds no parameter info but doesn't need to.

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?

The description clearly states it returns current UTC time in ISO-8601 and Unix timestamp formats, distinguishing it from sibling conversion tools like 'from_timestamp' and 'to_timestamp'.

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?

The description implies use when needing current time in specific formats, but lacks explicit when-not or alternatives. Context from siblings makes it clear, so still strong.

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

All Timestamp toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation2/5

Many tools occupy heavily overlapping territory: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, bet_research, validate_claim, and even entity_profile/compare_entities all route questions to similar underlying data and could easily be misselected. The Polymarket suite adds another cluster of near-synonymous tools. Descriptions are detailed, but the boundaries require careful reading to keep straight.

Naming Consistency2/5

Tool names mix imperative verbs (remember, subscribe, resolve_entity, validate_claim), noun-phrase descriptors (entity_profile, recent_changes, polymarket_edges), and time-utility names (now, from_timestamp, to_timestamp, relative_time). All-lowercase snake_case is consistent, but there is no unified verb_noun or domain-prefix pattern across the set.

Tool Count2/5

35 tools is heavy and exceeds the comfortable 3-15 range, and most of them are unrelated to the server name 'Timestamp,' which adds confusion. The broad Pipeworx data scope justifies more than a tiny utility server, but the count still feels overstuffed and will burden tool selection.

Completeness3/5

For the broad data-research and prediction-market domain the set actually covers, the lifecycle is fairly complete: query, deep research, entity profiles, comparisons, claim validation, subscription management, and memory storage all have working operations. However, the surface is sprawling and includes one-off tools like generate_llms_txt and scan_dependency that do not fit any coherent domain, making completeness hard to assess and leaving a fuzzy, fragmented impression.

Resources