Retrieves the relay configuration URL and opens it in your browser when possible, returning the URL, launch status, and current status.
Get the relay configuration URL for wet-mcp, opening it in the user's browser when possible. Returns the relay URL, whether the browser launched, and the current status.
| Name | Required | Description | Default |
|---|---|---|---|
| ctx | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v3.7.3v3.6.0v3.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the responsibility for disclosing behavior. It mentions the side effect of opening a browser 'when possible', and lists return values (URL, browser launched, status). However, it omits potential failures, permission requirements, or any side effects beyond the browser action.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two concise sentences, front-loaded with the primary purpose, and includes all essential behavioral information without superfluous details. It earns its length efficiently.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity and the presence of an output schema (likely documenting the return values), the description covers the core purpose and side effects adequately. It lacks details on error handling or integration with other tools, but for a straightforward config command it is sufficiently complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The only parameter is 'ctx', a standard context object, but the description does not mention or explain it. Schema coverage is 0% as the description adds no parameter-specific meaning. While the ctx parameter is typically auto-injected, the description should at least note its presence or purpose, making this a gap.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Get' and the resource 'relay configuration URL', and specifies the browser-opening behavior. It distinguishes itself from the sibling 'config' tool by focusing on the relay URL retrieval and browser action.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives, no preconditions, and no mention of when it should not be used. It simply states what the tool does without contextual advice.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.