Skip to main content
Glama
variflight

Variflight Tripmatch MCP Server

Official
by variflight

getTodayDate

Retrieve today's date in YYYY-MM-DD format from the Variflight Tripmatch MCP Server for accurate travel planning and booking operations.

Instructions

Get today's date in local timezone (YYYY-MM-DD format). Use this tool whenever you need today's date - NEVER hardcode dates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
random_stringNoDummy parameter for no-parameter tools

Implementation Reference

  • The handler function that computes today's date in the local timezone and formats it as YYYY-MM-DD, returning it in the MCP content format.
    }, async () => {
        const today = new Date();
        const year = today.getFullYear();
        const month = String(today.getMonth() + 1).padStart(2, '0');
        const day = String(today.getDate()).padStart(2, '0');
        const todayDate = `${year}-${month}-${day}`;
        return {
            content: [
                {
                    type: "text",
                    text: todayDate
                }
            ]
        };
    });
  • Zod input schema for the tool, featuring a dummy optional string parameter to satisfy MCP requirements for tools to have at least one parameter.
    random_string: z.string()
        .optional()
        .describe("Dummy parameter for no-parameter tools")
  • dist/index.js:166-184 (registration)
    The server.tool call that registers the 'getTodayDate' tool with the MCP server, including its description, input schema, and inline handler function.
    server.tool("getTodayDate", "Get today's date in local timezone (YYYY-MM-DD format). Use this tool whenever you need today's date - NEVER hardcode dates.", {
        random_string: z.string()
            .optional()
            .describe("Dummy parameter for no-parameter tools")
    }, async () => {
        const today = new Date();
        const year = today.getFullYear();
        const month = String(today.getMonth() + 1).padStart(2, '0');
        const day = String(today.getDate()).padStart(2, '0');
        const todayDate = `${year}-${month}-${day}`;
        return {
            content: [
                {
                    type: "text",
                    text: todayDate
                }
            ]
        };
    });
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses key behavioral traits: it returns today's date (not historical/future), uses local timezone (not UTC), and outputs in YYYY-MM-DD format. It doesn't mention error conditions, performance characteristics, or authentication needs, but for a simple date tool this is reasonably complete.

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 perfectly concise with two sentences that each earn their place: first states what the tool does with format/timezone details, second provides critical usage guidance. No wasted words, front-loaded with core functionality.

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 simple date-retrieval tool with no output schema, the description provides sufficient context: purpose, format, timezone, and usage guidance. It doesn't explain the return value structure beyond format, but for a simple string output this is adequate. The dummy parameter situation could be slightly confusing without schema inspection.

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?

The tool has 1 parameter with 100% schema description coverage, but the parameter is a 'Dummy parameter for no-parameter tools' according to the schema. The description correctly implies no meaningful parameters are needed by not mentioning any. It adds value by clarifying this is essentially a parameterless tool despite the schema structure.

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 purpose with specific verb ('Get') and resource ('today's date'), including format details ('YYYY-MM-DD format') and timezone context ('in local timezone'). It distinctly differentiates from sibling tools which are all flight/travel related, making this a standalone utility tool.

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 usage guidance: 'Use this tool whenever you need today's date - NEVER hardcode dates.' This gives clear when-to-use instructions and a specific prohibition against alternatives (hardcoding). No sibling tools overlap in functionality, so no comparative guidance is needed.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/variflight/tripmatch-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server