Skip to main content
Glama
Sign In
React Development Workflow MCP Server

React Development Workflow MCP Server

by rushit-simform
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_time

Get the current time, optionally in a specified timezone, to synchronize timestamps and scheduling across your workflow.

Instructions

Get the current time, optionally in a specific timezone

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

Input Schema

NameRequiredDescriptionDefault
timezoneNoTimezone (e.g., 'UTC', 'America/New_York')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries responsibility for behavioral disclosure. It mentions the optional timezone, which is a key behavior, but does not explain the default timezone, return format, or any other behavioral details. For a simple read-only tool, this is adequate but not rich.

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?

The description is a single concise sentence that directly conveys the essential information without any filler. It is appropriately sized for a simple tool and front-loads the core function.

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 tool with one optional parameter and no output schema, the description covers the essential use case. It does not detail default timezone behavior or output format, but these omissions are unlikely to prevent correct invocation for most simple use cases. The overall completeness is high for the tool's complexity.

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?

The input schema already documents the 'timezone' parameter with examples and indicates it's optional (0 required parameters). The description adds 'optionally' which reiterates the schema, providing marginal added meaning. With 100% schema coverage, a baseline of 3 is appropriate.

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 the tool's function with a specific verb ('Get') and resource ('current time'). It also distinguishes itself from sibling tools, none of which are time-related. The optional timezone parameter is highlighted, making the purpose unmistakable.

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?

The description implies when to use the tool (whenever current time is needed) but provides no explicit guidance or exclusions. There are no similar sibling tools, so ambiguity is low, but the description does not articulate usage context beyond the basic function.

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