Skip to main content
Glama
Sign In
Schwab MCP

Schwab MCP

by JackGuan99
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_current_time

Read-only

Returns the current date and time in US/Eastern exchange clock and UTC, providing a reliable baseline before performing date math.

Instructions

Current date and time in US/Eastern (the exchange clock) and UTC. Useful before date math.

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

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the agent knows this is a safe, closed-world read. The description adds one piece of genuine context — that US/Eastern is 'the exchange clock,' implying which timezone matters for trading decisions — but says nothing about precision, caching, or freshness.

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 compact clauses with the timezones front-loaded and the usage hint trailing. Every word earns its place and nothing is repeated from the schema or annotations.

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?

With no parameters and an output schema that already documents the returned fields, the description only needs to frame what clock is returned and why; it does that. Minor gap: no indication of timezone format (e.g. ISO 8601) or freshness guarantees.

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?

There are zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly avoids padding with nonexistent arguments.

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 resource (current date and time) with concrete scope: US/Eastern and UTC. Clear enough that an agent instantly distinguishes it from siblings like get_market_hours, though it doesn't name those alternatives explicitly.

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 phrase 'Useful before date math' gives an implied usage context, but there is no when-to-use vs. when-not guidance and no named alternatives among the many sibling tools that also return time-related data (e.g. get_market_hours).

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