Skip to main content
Glama

Notificar oferta o lanzamiento de Steam al telefono (Discord)

notificar_oferta_steam
Destructive

Sends Steam deal, featured game, or new release alerts to your phone via Discord webhook, with a Windows popup and optional Steam client launch.

Instructions

Envía una notificación al teléfono del usuario a través de un Webhook de Discord (DISCORD_WEBHOOK_URL) con ofertas, juegos destacados o nuevos lanzamientos. También muestra un aviso emergente en Windows y opcionalmente abre el juego en el cliente local de Steam.

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": {
      "titulo": "<titulo>",
      "mensaje": "<mensaje>",
      "confirmar": "<confirmar>"
    },
    "name": "notificar_oferta_steam"
  }
}

Input Schema

NameRequiredDescriptionDefault
appidNoAppID opcional de un juego principal para adjuntar su portada y enlace directo a la tienda
tituloYesTitulo de la alerta (ej: 'Nuevas ofertas y lanzamientos en Steam')
mensajeYesCuerpo del mensaje con los juegos, precios, descuentos y enlaces
confirmarYesConfirmacion obligatoria (true) para autorizar el envio de la notificacion al telefono
abrir_en_steam_pcNoSi es true, abre ademas la tienda de Steam en el cliente local del PC

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=true), the description discloses the concrete side effects: an external message is posted to Discord via a webhook, a Windows popup appears, and the local Steam client may be opened. It does not contradict the destructive hint, but it omits failure behavior (e.g., missing webhook config) and whether delivery is idempotent or rate-limited.

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

Conciseness4/5

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

Two dense sentences, front-loaded with the primary action and channel, with secondary effects (popup, Steam client) following. Nothing is redundant, though the second sentence packs two distinct effects together without separating the optional one clearly.

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?

For a 5-parameter mutation tool with no output schema and only minimal annotations, the description covers the visible side effects but leaves gaps: no return/confirmation behavior, no precondition about the webhook being configured, and no note that 'confirmar' must be true. An agent could still call it, but with residual uncertainty about failure modes.

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?

With 100% schema description coverage, the schema already documents all five parameters, so baseline 3 applies. The description only loosely echoes appid (cover/link) and abrir_en_steam_pc, and actually says it 'opens the game' while the schema says it opens the Steam store — a minor mismatch that adds ambiguity rather than meaning.

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 names a specific verb+resource+channel: it sends a notification to the user's phone via a Discord webhook about deals, featured games, or new releases, plus a Windows toast and optional Steam client launch. This clearly separates it from the read-only sibling tools (buscar_ofertas_steam, detalle_juego_steam, etc.), which only retrieve data.

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 implied by the content it carries (offers, featured games, new releases), so an agent can infer it is the delivery step after a search. However, there is no explicit when-to-use/when-not guidance, no mention of prerequisites such as a configured DISCORD_WEBHOOK_URL, and no instruction on sequencing with siblings like buscar_ofertas_steam.

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