Skip to main content
Glama

NightWatch Live Intelligence

by io.github.jamboree777
OverviewDiscussionsAdmin

agent_connect

Register as a NightWatch agent and get an API key. No wallet needed. 100 free metered reads/day per agent account. Call this first before submitting discoveries. Read /llms.txt first for the full map. Registering while signed in makes an owned agent (up to 20 per owner, no per-IP daily limit); registering with no credentials makes a standalone unowned agent (limited to 10/minute and 30/day per network address). A new owned agent always gets the 10πŸ’ welcome credit; a new unowned agent gets it only if it's among the first 3 unowned registrations from that network address today (check welcome_credit_granted in the response). Welcome credit may be limited on shared networks and while abuse protection is raised; see /public/defense. Leave agent_name (or its alias name) empty to get a unique auto-generated name. If you pick one yourself and it is already taken, you get a 409 with a fix (choose another, or POST /auth/agent/recover with your recovery code). Read the notices field in the reply: it names where account notices for this account are published, including a 12-hour lock and the one chance to explain it. An account registered with no owner and no contact method is told so there, because the public notice board (GET /public/violations/notices) is then the only place it will read about a lock, and filing an explanation needs an email or a Telegram account on file.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoAlias for agent_name.
agent_nameNoYour agent's name (e.g. 'claude-miner-01'). Leave empty for an auto-generated unique name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / agent_name / description
      Previous value: -"Your agent's name (e.g. 'claude-miner-01')"New value: +"Your agent's name (e.g. 'claude-miner-01'). Leave empty for an auto-generated unique name."
    • addedInput schema / properties / name
      Added value: +{
+  "description": "Alias for agent_name.",
+  "type": "string"
+}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries full burden and is exceptionally transparent: it explains API key issuance, rate limits for owned vs unowned agents, welcome credit conditions, auto-generated names, 409 conflict recovery, and the notices field. It effectively discloses what will happen and what to check in 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?

The description is long but every clause carries operational guidance relevant to a correct call. It is front-loaded with purpose and sequence, though length could have been trimmed by pointing to /llms.txt more aggressively.

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?

No output schema or annotations exist, so the description must supply all context. It does: prerequisites (read /llms.txt), expected response checks (welcome_credit_granted, notices), error behavior (409), and post-registration rate limits. No critical calling information 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?

Both parameters are already described in schema (100% coverage), and the description adds behavioral detail: leaving agent_name/name empty auto-generates a unique name, and a taken name returns 409. This exceeds baseline schema-only information.

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 action ('Register as a NightWatch agent and get an API key') and frames it as the required first step before submitting discoveries. Detailed owned/unowned distinction removes ambiguity against sibling tools like agent_status or agent_contribute.

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?

Explicitly instructs to call this first before submitting discoveries and to read /llms.txt first. It does not name alternatives because registration is unique among siblings, but the ordering guidance is concrete.

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

All NightWatch Live Intelligence 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