Skip to main content
Glama
variflight

Variflight Tripmatch MCP Server

Official
by variflight
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

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

  • dist/index.js:170-184 (handler)
    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
            }
        ]
    };
});
  • dist/index.js:167-169 (schema)
    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
            }
        ]
    };
});

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
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 of behavioral disclosure. It effectively describes the tool's behavior: it returns today's date in a specific format and timezone. However, it doesn't mention potential edge cases (e.g., timezone handling during daylight saving) or error conditions, leaving some behavioral aspects unspecified.

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 extremely concise (two sentences) and front-loaded with the core functionality. Every sentence earns its place: the first defines the tool's output, and the second provides critical usage guidance. There is zero wasted text.

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?

Given the tool's low complexity (no parameters, simple output), no annotations, and no output schema, the description is complete enough. It specifies the exact format and timezone of the return value, and the usage guidance covers when to invoke it. For this simple tool, no additional context is needed.

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 input schema has 100% coverage with a single dummy parameter, so the schema already documents it. The description correctly indicates this is essentially a no-parameter tool by focusing on the date retrieval without mentioning inputs. It adds value by clarifying the tool's parameterless nature implicitly through its usage focus.

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 specific verb ('Get') and resource ('today's date'), with precise format details ('YYYY-MM-DD format') and timezone context ('local timezone'). It distinctly differentiates from sibling tools which are all flight-related, making its purpose unambiguous.

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' and 'NEVER hardcode dates.' This gives clear when-to-use instructions and a specific prohibition, helping the agent choose this tool over manual date handling or other date-related tools.

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