Skip to main content
Glama

delete_game_review

Delete your review of a game with safeguards: drafts require confirm=true, and published reviews also require published=true to prevent accidental removal.

Instructions

Delete your review of a game. Drafts need confirm=true. A published review also needs published=true, so it is never removed by accident.

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

Input Schema

NameRequiredDescriptionDefault
slugYes
confirmNo
publishedNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • removedInput schema / properties / wait_ms
      Removed value: -{
      -  "default": 3000,
      -  "title": "Wait Ms",
      -  "type": "integer"
      -}
  2. First observedv1.0.1

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose the key behavioral trait: this is a destructive, irreversible-sounding operation protected by two explicit confirmation flags, with the stated intent that a published review 'is never removed by accident'. It stops short of stating permission requirements or what the response contains, but the safety model is clearly communicated.

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?

Three short sentences, front-loaded with the action, then the two guard conditions in increasing order of caution. No filler or repetition.

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 not be explained, and the description covers the critical safety logic an agent needs before invoking a destructive tool. The remaining gap is the unexplained 'slug' parameter and the absence of any note on whether deletion is permanent or recoverable.

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%, so the description must compensate. It explains the meaning and conditional requirement of 'confirm' and 'published' (draft vs published state), but leaves 'slug' completely undefined and does not specify how the two booleans interact if both are needed or supplied incorrectly.

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 states a specific verb and resource ('Delete your review of a game'), which is unambiguous and clearly distinct from add_game_review. It does not explicitly name or contrast with any sibling, but the resource is narrow enough that misselection is unlikely.

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?

It gives conditional preconditions for the two guard flags ('Drafts need confirm=true', published reviews need published=true), which is useful context for calling the tool. However, it never states when to use this tool versus alternatives (e.g., editing or removing review content another way), nor does it mention what happens if the flags are omitted or mismatched.

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