Skip to main content
Glama
Sign In
epic-gog-free-games-mcp

epic-gog-free-games-mcp

by OnTarget600
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

epic_free_games_upcoming

List announced upcoming free games on Epic Games Store with their release dates, based on country.

Instructions

List the NEXT free games coming to the Epic Games Store (announced upcoming giveaways), with the date each becomes free.

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": "epic_free_games_upcoming"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoISO country code (default US).US

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations provided. Description says it lists games with dates, but does not disclose potential rate limits, pagination, data freshness, or output structure beyond 'date each becomes free'.

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?

Single sentence, front-loaded with key information ('list the NEXT free games'), no unnecessary words.

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 list tool with one optional parameter, the description covers the main purpose and what to expect (dates). Could hint at output format but overall sufficient.

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?

Only parameter 'country' is documented in schema with default and description. Tool description adds no extra meaning beyond what schema already provides.

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 explicitly states it lists 'NEXT free games' on Epic Games Store with dates, clearly differentiating from 'current' giveaways and GOG siblings via naming and context.

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

Usage Guidelines4/5

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

The phrase 'NEXT free games' and mention of 'announced upcoming giveaways' implies using for future giveaways, distinct from current. No explicit when-not-to-use, but sibling names provide context.

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