Skip to main content
Glama

Save an alert

save_alert
Idempotent

Save a person/topic slug or literal keyword phrase. RSS only by default; never enables Following consent. Paid email needs separate consent. Needs account scope. Free.

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": {
      "kind": "<kind>"
    },
    "name": "save_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
slugNo
alertNo
keywordNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare the write/idempotent/non-destructive profile, yet the description adds real behavioral context beyond them: it never enables Following consent, paid email requires separate consent, account scope is required, and the operation is free. Those consent and billing semantics are exactly the kind of thing structured fields cannot express. It does not describe side effects on existing alerts or the response.

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?

Five short clauses, front-loaded with the primary action and payload, with zero filler. The telegraphic fragment style ('Free.') is efficient but costs a little readability compared with full sentences.

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 small 4-parameter mutation with annotations and no output schema, the consent, scope, and cost context makes it broadly usable. The gaps are the unstated kind-to-field mapping and the meaning of the alert delivery enum, which an agent must guess from the schema alone.

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 carries the burden and only partly discharges it. It maps 'person/topic slug' to the slug field and 'literal keyword phrase' to the keyword field, and 'RSS only by default' hints that the alert enum defaults to rss. It never explains the daily/weekly/rss enum values, which value is required for which kind, or the 200-character limits.

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?

States a specific verb (Save) and resource (alert) and immediately narrows it to 'a person/topic slug or literal keyword phrase', which tells an agent what the payload is. It does not name or differentiate itself from siblings like update_alert or list_saved_alerts, so it stops short of a 5.

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?

Implied creation semantics plus useful preconditions ('Needs account scope') and defaults ('RSS only by default'). However there is no explicit guidance on when to use this versus update_alert/remove_alert, nor on what happens if an alert already exists given idempotentHint=true.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources