Skip to main content
Glama

set_game_rating

Set or update a game's 1–10 overall rating and optional gameplay, story, visual, audio, and playability sub-ratings, or clear the rating.

Instructions

Rate a game 1-10 overall, with optional 1-10 sub-ratings for Gameplay, Story, Visual, Audio and Playability. Ratings are per game, not per copy. clear=true removes your rating. Sub-ratings you leave blank keep their current value.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "set_game_rating"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes
audioNo
clearNo
scoreNo
storyNo
visualNo
wait_msNo
gameplayNo
playabilityNo
collection_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.1.0
    • addedInput schema / properties / audio
      Added value: +{
      +  "default": "",
      +  "title": "Audio",
      +  "type": "string"
      +}
    • addedInput schema / properties / collection_id
      Added value: +{
      +  "default": "",
      +  "title": "Collection Id",
      +  "type": "string"
      +}
    • removedInput schema / properties / sound
      Removed value: -{
      -  "default": "",
      -  "title": "Sound",
      -  "type": "string"
      -}
    • changedInput schema / properties / wait_ms / default
      Previous value: -3000New value: +0
  2. First observedv1.0.1

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it discloses that ratings are game-scoped rather than copy-scoped, that clear=true is a destructive operation, and that omitted sub-ratings are preserved rather than reset. It omits auth/permission requirements and says nothing about how numeric ratings are supplied even though the schema types them as strings.

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?

Four short sentences, front-loaded with the primary action and followed by scope, deletion behavior, and partial-update rules. No filler, and each sentence adds a distinct fact an agent needs.

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?

An output schema exists so return values need no explanation, and the description covers the mutation semantics well for a 10-parameter tool. The remaining gap is the two undocumented parameters (collection_id, wait_ms) and the absence of any error or validation guidance, which is minor but real for an unannotated write tool.

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 0% across 10 parameters, so the description must compensate; it explains score, clear, and the five sub-ratings reasonably well but leaves collection_id and wait_ms entirely undefined, and never explains that slug is the game identifier. The mismatch between the stated "1-10" range and the string-typed score fields is also unaddressed.

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?

States a specific verb and resource ("Rate a game 1-10 overall") plus the exact sub-rating dimensions, and adds the crucial scope qualifier "per game, not per copy." That scope line implicitly separates it from copy-level sibling tools like set_game_acquisition, so an agent can distinguish intent without opening a schema.

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?

Gives clear operating context: use clear=true to remove a rating, and blank sub-ratings preserve their current value (partial-update semantics). It does not name an alternative such as add_game_review for written reviews or state when-not to use it, so the routing guidance is strong but not exhaustive.

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