Analyzera

Set alerts

set_alerts

DestructiveIdempotent

Email alerts, as one daily digest, on a strategy ('rebalance', 'risk') or an account ('risk', 'drift' from the strategy it tracks). Replaces the kinds set on that subject; [] turns them off. threshold: a risk-level step (default 0.5) or a drift share (default 0.05).

'pre_rebalance' on a strategy emails its next target weights from 12:00 Stockholm
on the weekday before it trades. A linked account gets it without asking; leaving
it out of ``kinds`` turns it off.

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": {
      "subject_id": "<subject_id>",
      "kinds": "<kinds>"
    },
    "name": "set_alerts"
  }
}

Input Schema

Name	Required	Description	Default
`kinds`	Yes
`threshold`	No
`subject_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A3.7/5.0

Behavior4/5

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

With annotations declaring destructiveHint=true and idempotentHint=true, the description adds meaningful behavior: it replaces existing kinds, [] disables alerts, threshold defaults are 0.5 or 0.05, and pre_rebalance triggers emails from 12:00 Stockholm on the prior weekday. It also notes linked accounts inherit pre_rebalance automatically. This is valuable context beyond the annotations, though auth and error behavior are not covered.

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?

The description is front-loaded with the primary action and then details replacement semantics and pre_rebalance behavior. Every sentence contributes useful information, though the second paragraph is somewhat dense and could be slightly tighter.

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 annotations already cover safety and idempotency. The description fills in replacement behavior, defaults, and scheduling details, but leaves subject_id semantics unstated and does not point to get_alerts for viewing current alerts.

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 carry the burden. It explains kinds per subject ('rebalance', 'risk' on a strategy; 'risk', 'drift' on an account), covers 'pre_rebalance' behavior, and gives threshold defaults (0.5 for risk step, 0.05 for drift share). However, subject_id is only implied to be a strategy or account identifier, not explicitly described as an integer ID, and the array nature of kinds is not stated.

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 opens with a specific verb and resource: 'Email alerts, as one daily digest, on a strategy ... or an account.' It clearly states what the tool does and for which subjects. It does not explicitly name the sibling get_alerts to distinguish setting from reading, which keeps it at 4 rather than 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?

The description gives clear operational context such as 'Replaces the kinds set on that subject; [] turns them off,' which implies how to use the tool. However, it never says when to use this versus get_alerts or other alert-related siblings, leaving alternative 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 Analyzera tools Inspect

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

Need Help?