DEBYKO

DEBYKO read an alert rule

agent_rule_get

Read-onlyIdempotent

Reads one of your saved DEBYKO Agent alert rules by rule_id or exact label. Returns its original persisted DQL condition, label, status, interval, channels, last firing and history (times it would have fired in 30 days; past fact). Sends nothing, no evaluation budget. No webhook URL or credential. Requires an account key. Not counted on your key. Use this when the user asks what a named DEBYKO rule checks, requests its DQL, or wants that rule explained (also: что проверяет правило); for current true/false state use agent_state.

Input Schema

Name	Required	Description	Default
`label`	No	The exact visible rule label, for example BYKO_V2_BREAKOUT_LONG. If labels collide, use rule_id from agent_state.
`rule_id`	No	The rule's id, as agent_rule_create returned it or agent_state lists it.

Output Schema

Name	Required	Description	Default
`enabled`	No
`history`	No
`channels`	No
`interval_s`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 22, 2026
- addedOutput schema / properties / history
```
Added value: +{
+  "type": "object"
+}
```

Changed1 schema field changedOct 13, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "patternProperties": {
+    "^(?:label|paused_by|paused_reason|timeframe|last_fired_at)$": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "^(?:rule_id|name|status|mode|kind|created_at|dql)$": {
+      "type": "string"
+    }
+  },
+  "properties": {
+    "channels": {
+      "type": "array"
+    },
+    "enabled": {
+      "type": "boolean"
+    },
+    "interval_s": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

AddedOct 11, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description goes further: it states no evaluation budget is consumed, nothing is sent or fired, no webhook URL or credential is exposed, and it is not counted on the caller's key. It also flags that `history` is a past-fact projection (would have fired in the last 30 days), which prevents a common misinterpretation.

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 core action and return fields are front-loaded in the first sentence, with usage routing second. The middle stretch is a series of short negations ("Sends nothing, no evaluation budget. No webhook URL...") that each carry real information but read as a list rather than prose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists so return values needn't be detailed, yet the description still characterizes the non-obvious `history` field and the persisted-vs-live DQL distinction. With annotations covering the safety profile and 100% schema coverage on params, nothing an agent needs to call this correctly is missing.

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 coverage is 100% and the schema already explains label collision handling and where rule_id comes from, so the description's "by rule_id or exact label" adds little beyond it. Baseline 3 is appropriate; the schema is doing the parameter work.

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 ("Reads one of your saved DEBYKO Agent alert rules") plus the lookup keys (rule_id or exact label), and enumerates the returned payload. It explicitly differentiates itself from agent_state, which is the nearest sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger ("when the user asks what a named DEBYKO rule checks, requests its DQL, or wants that rule explained") and names the alternative for the adjacent need ("for current true/false state use `agent_state`"). Even a non-English phrasing trigger is included, leaving little to inference.

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

All DEBYKO 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?