Skip to main content
Glama
Sign In

Realtap

by io.github.CSteenkamp
OverviewDiscussionsAdmin

List your alert rules and delivery targets

list_alerts
Read-onlyIdempotent

The alert rules your API key created, the account's delivery targets (signing secrets are never shown) and the most recent deliveries with their status, so you can see whether a webhook is working. Only a key's own rules can be changed, deleted or tested; with all the account's other rules (made on the website or by other keys) are listed too, read-only (own: false), wallet addresses cut to a prefix and without their targets. Needs an API key.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_alerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
allNoAlso list the account's other rules, read-only and redacted.
deliveriesNoHow many recent deliveries to include (0-20, default 5).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/destructive annotations, it discloses that signing secrets are never returned, that addresses are truncated to a prefix and targets omitted for other keys' rules, and that an API key is required. That is exactly the kind of redaction and auth context annotations cannot express.

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?

Content is front-loaded with what is returned, then scoping, then auth — a sensible order with no filler. The middle sentence is long and clause-stacked, which slightly hurts scannability.

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?

With no output schema, the description carries the job of describing returns and does enumerate the three returned components plus status. Minor gaps remain (ordering of deliveries, whether targets are reusable via other tools), but nothing an agent needs to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema: it explains that `all` returns records with `own: false`, truncated wallet addresses and no delivery targets. `deliveries` is left entirely to the schema, which is acceptable given it is fully documented there.

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 and three concrete resources (alert rules, delivery targets, recent deliveries) rather than restating the title. It is clearly distinguishable from the mutation siblings create_alert, delete_alert and test_alert, which the 'can be changed, deleted or tested' clause implicitly separates it from.

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

Usage Guidelines4/5

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

It gives a concrete reason to call the tool ('so you can see whether a webhook is working') and explains exactly when to set `all` and what the trade-off is (read-only, redacted, own:false). It stops short of an explicit 'do not use this for X, use Y instead' exclusion, so a 4 rather than a 5.

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

All Realtap toolsInspect
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