Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

date-month

Generate a random month name, optionally abbreviated or formatted for date context, to create realistic fake date data.

Instructions

Returns a random name of a month.

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": "date-month"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextNoWhether to return the name of a month in the context of a date. In some locales this may affect grammar or capitalization.
abbreviatedNoWhether to return an abbreviation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the most important trait — the result is randomly generated, not derived from a date — but it says nothing about the return being a plain string, whether it is locale-sensitive, or that the two flags alter the output shape.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with zero filler, which is appropriate for a trivial generator. It is slightly under-specified rather than verbose, but nothing is wasted.

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

Completeness3/5

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

For a simple two-optional-parameter tool with no output schema, the definition covers the core behavior (random month name) but not the return format or how abbreviated/context change it. An agent can call it, but must open the schema to understand the output variants.

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?

Schema description coverage is 100%, so both booleans are already documented in the schema. The description adds nothing about context or abbreviated, leaving the schema to do all the work — the expected baseline of 3.

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?

"Returns a random name of a month" states a specific verb (returns) and resource (month name) plus the key attribute that it is random. It does not explicitly differentiate itself from date-weekday or date-anytime, so an agent must infer the distinction from the resource noun alone.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of when a random month is preferable to date-anytime or date-weekday, and no note about when to set abbreviated or context. The agent gets the purpose but no routing or invocation guidance.

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