Skip to main content
Glama
Sign In

BotsRated (beta)

by com.botsrated
OverviewDiscussionsAdmin

Watch free (email)

watch_free

Call this when you want an email only when a covered host's measured facts change. Free. Same watch as POST /v1/alerts/subscribe: 1 covered host, email only, at most once per UTC day when measured facts change, 30 days, up to 3 active watches per client. The confirmation email is the existing alerts email. Not a price change. Slack, Discord and webhook stay on a paid plan. The success payload returns handle, the same value as token, shown once. Next step: confirm the email, then call what_changed with that handle.

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": {
      "host": "<host>",
      "email": "<email>"
    },
    "name": "watch_free"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYesSeller hostname or URL, e.g. blockrun.ai or https://blockrun.ai/api/v1/chat/completions
emailYesEmail for the confirmation link and later change emails

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say this is a non-read-only, non-destructive, non-idempotent write; the description goes far beyond by disclosing frequency caps, watch duration, per-client watch limit, that the handle/token is shown only once, and that the confirmation email is the existing alerts email. For a subscription-creating mutation that is exactly the context an agent needs.

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?

Front-loads the triggering condition and price information, then layers limits, exclusions, and next step. Dense but nearly every clause carries operational weight; the middle run of quota clauses is slightly cramped into one sentence.

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?

Despite no output schema, the description explains the success payload (handle, same as token, shown once) and the exact next call. Combined with the quota and channel details, nothing an agent needs to invoke and follow up 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% with two self-documented parameters, so the baseline is 3; the description earns an extra point by constraining `host` to a *covered* host (pointing at the coverage sibling) and clarifying that the email drives both the confirmation link and later change notifications.

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 concrete action (create a free email-only watch that fires when a covered host's measured facts change) and immediately delimits it against the paid Slack/Discord/webhook path and against price-change alerts. The agent knows exactly what this tool creates without inspecting the schema.

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 explicit triggering conditions ('when you want an email only when a covered host's measured facts change'), exclusions ('Not a price change', paid channels), hard quotas (1 host, once per UTC day, 30 days, 3 active watches) and the follow-up sequence (confirm email, then call what_changed with the handle). Little is left to inference.

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

All BotsRated (beta) 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