Skip to main content
Glama

Open a Wake desk for a website

wake_signup
Read-only

Create the account and the desk for a website you own and get an API key back, so you can install the tracker and read the desk over MCP. Needs site, email and terms_accepted: true (terms: /wake/docs/terms.md, privacy: /wake/docs/privacy.md). One desk per host; rate-limited.

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": "wake_signup"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoThe website, e.g. https://docs.example.com
emailNoThe owner's email; the desk sign-in and the weekly brief go there.
terms_acceptedNotrue once the Terms and Privacy policy are accepted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior1/5

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

The annotations declare readOnlyHint=true, but the description explicitly says the tool 'Create[s] the account and the desk' and returns an API key — an unmistakable state mutation. This is a direct contradiction of the supplied annotations, so the score is 1 regardless of the otherwise useful details about rate limits and the one-desk-per-host rule.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences that front-load the action and outcome, then the prerequisites and limits. Every clause carries information — no filler, no restatement of the name or title.

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?

For a three-parameter signup tool with no output schema, the description covers the purpose, the returned API key, prerequisites, linked legal docs, and the one-desk and rate-limit constraints. What's missing is failure behavior, e.g. what happens if the host already has a desk, which matters given the sibling wake_check_site.

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?

The schema already documents all three parameters at 100% coverage, but the description adds meaning the schema lacks: it states all three are effectively required despite required=0 in the schema, and it supplies the terms and privacy document paths needed to legitimately set terms_accepted to true.

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 uses a specific verb+resource pair ('Create the account and the desk for a website you own') and states the concrete outcome ('get an API key back'), which clearly separates a signup action from siblings like wake_about and wake_check_site.

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 establishes clear context for when to call: the user owns the site, needs the tracker installed, or wants MCP access to the desk. It also gives a prerequisite constraint ('One desk per host; rate-limited'), but it never explicitly says what to do if a desk already exists or names an alternative tool for that case.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources