Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

date-weekday

Generates a random day of the week, optionally abbreviated or formatted in date context, for fake data generation and testing.

Instructions

Returns a random day of the week.

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-weekday"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextNoWhether to return the day of the week 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.3/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 burden. It does disclose the key behavioral trait that the result is randomly generated rather than a fixed lookup, which is the most important thing to know. It stops short of describing the return shape (e.g. whether the value is a full name or an index) or any locale dependence.

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?

A single short sentence, front-loaded with the verb and resource, with zero filler. Nothing needs trimming.

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?

This is a very simple tool with fully described parameters, so little prose is required. However, with no output schema, the description never indicates what the returned value looks like, which is a real gap for a generator whose output could be a name, an abbreviation, or a contextualized string.

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%, and the two boolean parameters are fully documented in the schema itself, including the locale/grammar nuance of 'context' and the abbreviation behavior. The description adds no parameter meaning beyond that, so the baseline of 3 applies.

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?

The description gives a specific verb and resource: it returns a random day of the week name. An agent can immediately tell this generates a weekday string rather than a date or a month. It does not, however, contrast itself with siblings such as date-month or date-anytime, so differentiation is left to the name.

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 alternatives, and no statement of prerequisites or exclusions. The agent must infer from the tool name alone that this is the right pick over date-month or date-anytime.

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