Metadata MCP Connector

Get Current Date

get_current_date

Read-only

Return the REAL current date and time (UTC).

            WARNING: You do NOT inherently know today's date — never guess it or
            rely on training-time assumptions. Whenever a task depends on
            "today" — setting campaign/budget start & end dates, interpreting
            "this month" / "next quarter" / "last 30 days", validating that an
            endDate is in the future, or any relative date math — you MUST
            anchor to the real current date. If you are not already certain
            what today is, CALL THIS TOOL FIRST and use its `current_date`
            for all subsequent date calculations.

            Takes no parameters.

            RETURNS:
            {
                "current_date": "2026-09-30",
                "current_datetime_utc": "2026-09-30T12:00:00.000Z",
                "current_year": 2026,
                "current_quarter": "Q3",
                "timezone": "UTC"
            }

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 16, 2026

TDQS

A5/5.0

Behavior5/5

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

While annotations already declare readOnlyHint=true and destructiveHint=false, the description adds crucial behavioral context: it warns that the agent does not inherently know today's date and must not guess, which is a key cognitive trap. It also discloses the exact return format including fields like current_date, current_datetime_utc, and timezone, providing transparency beyond the annotations.

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 well-structured: it leads with the core purpose, then a critical warning, followed by use cases, a note on parameters, and the return format. Each section serves a distinct purpose without redundancy. It is thorough yet not bloated, with the most important guidance (do not guess dates) prominently placed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter tool with no output schema, the description is exceptionally complete. It covers the purpose, usage triggers, and provides the full return JSON structure, including field names and example values. There is nothing an agent needs to know that is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, and the description explicitly states 'Takes no parameters.' This eliminates any ambiguity about invocation. Since schema coverage is 100% (trivially) and the description confirms the absence of parameters, it fully clarifies the interface.

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: 'Return the REAL current date and time (UTC).' It specifies the exact verb and resource, making it unambiguous. It also distinguishes itself from any potential date-related assumptions by emphasizing the 'REAL' current date, which is unique among the sibling tools.

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

Usage Guidelines5/5

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

The description provides explicit when-to-use guidance, listing concrete scenarios such as 'setting campaign/budget start & end dates,' 'interpreting this month / next quarter / last 30 days,' and 'validating that an endDate is in the future.' It even instructs the agent to 'CALL THIS TOOL FIRST' if unsure, leaving no doubt about when to invoke it.

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

All Metadata MCP Connector tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?