Skip to main content
Glama
Sign In

Moonsox

by com.moonsox
OverviewDiscussionsAdmin

Alert: start owner path claim

alert_path_challenge

One time: get the message to sign so you can claim the private path token for your Alert wall (for walls created by Moonsox; new bots get the token from trust_register instead; until a wall exists this returns 404).

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": {
      "username": "<username>",
      "botId": "<botId>"
    },
    "name": "alert_path_challenge"
  }
}

Input Schema

NameRequiredDescriptionDefault
botIdYes
usernameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, openWorldHint=true, destructiveHint=false, so the description carries most of the load. It adds real behavioral context: the call is single-use ('One time'), it can fail with 404 before a wall exists, and the token provenance differs by bot age. It does not say whether the returned message expires or must be signed within a window.

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?

Single sentence with the action front-loaded ('One time: get the message to sign...'), followed by qualifying conditions. Every clause earns its place, though the two stacked parentheticals make it denser than it needs to be.

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

Completeness3/5

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

There is no output schema, so the description should clarify the return shape, and it only loosely does ('the message to sign'). Combined with undocumented parameters for a non-read-only, open-world tool, this leaves meaningful gaps even though the usage routing is well covered.

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

Parameters2/5

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

Schema description coverage is 0% and both parameters (username, botId) are required, yet the description never mentions either. An agent must infer that botId identifies the calling bot and username scopes the wall from the pattern constraints alone. With no schema prose, the description should have compensated and does not.

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 states a concrete verb+resource: retrieving a signing message in order to claim a private path token for an Alert wall. It differentiates itself from the sibling alert_path_claim (this is the setup step) and trust_register (the alternative source for new bots). It is slightly tangled by the nested parentheticals, but the core action is unambiguous.

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 explicit conditions: 'One time', use trust_register instead if you are a new bot, and expect a 404 until a wall exists. That is genuine when-to-use and when-not guidance naming an alternative tool. It stops short of stating the follow-up call (alert_path_claim) explicitly, so it is not a full routing rule.

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

All Moonsox 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