Skip to main content
Glama
Sign In

NestDaddy

by com.nestdaddy
OverviewDiscussionsAdmin

games

Read-onlyIdempotent

Games, updated daily from Steam: top sellers, new releases, coming soon, deals and the most played right now, with description, genre, platforms, price, release date, rating (0-10 from player reviews) and players_now. query: optional words (title, genre or developer). genre: all, action, adventure, rpg, strategy, sports, racing, puzzle, simulation. sort: trending (most played now), latest (newest releases), rating or name. limit: 1-50.

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

Input Schema

NameRequiredDescriptionDefault
sortNoOrder: latest (newest first), trending (most used or played), name (A-Z) or rating.trending
genreNoall, action, adventure, rpg, strategy, sports, racing, puzzle or simulation.all
limitNoHow many results to return, 1-50. Values outside the range are clamped.
queryNoOptional key words: a name, use, vendor or developer. Empty lists everything.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / genre / description
      Added value: +"all, action, adventure, rpg, strategy, sports, racing, puzzle or simulation."
    • addedInput schema / properties / limit / description
      Added value: +"How many results to return, 1-50. Values outside the range are clamped."
    • addedInput schema / properties / query / description
      Added value: +"Optional key words: a name, use, vendor or developer. Empty lists everything."
    • addedInput schema / properties / sort / description
      Added value: +"Order: latest (newest first), trending (most used or played), name (A-Z) or rating."
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds genuinely new context beyond them: the data source (Steam), the daily refresh cadence, and the fact that rating is a 0-10 player-review score while players_now is live concurrency. It omits pagination or rate-limit behavior, which keeps it below 5.

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

Conciseness3/5

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

The opening clause front-loads the resource and scope effectively, which is good. However, the second half is a run-on blob that duplicates the schema's genre list, sort definitions and limit range almost word for word, so several clauses do not earn their place.

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?

With an output schema present, return fields do not need full explanation, and annotations carry the safety profile, so the remaining burden on the description is light. It covers source, freshness, and filtering inputs adequately, missing only sibling differentiation and any note on result ordering ties or empty-result behavior.

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 the baseline is 3. The description largely restates the schema verbatim — repeating the full genre enum, the sort interpretations, and the 1-50 limit range — and adds no new semantics such as query matching rules (prefix vs substring) or what happens with combined query+genre filters.

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 names a specific resource (Steam games) with explicit scope: top sellers, new releases, coming soon, deals, most played. It is clear this is a catalog-listing tool, but it never distinguishes itself from siblings like software or web_search, so an agent must infer the boundary itself.

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

Usage Guidelines3/5

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

Usage is only implied through the parameter semantics: 'query: optional words' suggests searching within the games catalog and 'sort: trending (most played now)' suggests discovery. There is no explicit when-to-use, when-not-to-use, or named alternative among the sibling tools, leaving selection to inference.

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

All NestDaddy toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources