Skip to main content
Glama

AskFur pet devices (pre-launch)

Join the AskFur launch waitlist

join_waitlist
Idempotent

Adds the person's own email to AskFur's launch-updates waitlist. Only call after the person has agreed. Nothing is bought and no email is sent now. Returns a private removal code the person can use on askfur.com/preview to leave the list.

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": {
      "email": "<email>",
      "consent": "<consent>"
    },
    "name": "join_waitlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesThe person's own email address, which they asked to add. Never someone else's.
consentYesMust be true: the person agreed to receive AskFur launch updates by email at this address.
productNoWhat they want updates about: a product slug from list_products, or general for the whole brand. Defaults to general.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare non-read-only, non-destructive, idempotent behavior, and the description adds genuinely new context: nothing is purchased, no email is sent at call time, and a private removal code enables the person to undo the signup. That is exactly the side-effect and reversibility information an agent needs before mutating state.

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?

Four short sentences, front-loaded with purpose and then the consent precondition, side effects, and return value. Every sentence carries information; only the 'own email' emphasis slightly overlaps with the schema.

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?

With no output schema, the description compensates by explaining what is returned (a private removal code) and where it is used. Combined with the consent gate and the no-email-sent clarification, an agent has everything needed to call this correctly and safely.

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

Parameters3/5

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

Schema coverage is 100%, so the schema already documents all three parameters including the ownership constraint on email and the meaning of consent. The description restates the 'person's own email' rule rather than adding new semantics, so the baseline 3 applies.

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 verb and resource ('Adds the person's own email to AskFur's launch-updates waitlist') and scopes it to the caller's own address, which cleanly separates it from the read-only siblings get_product and list_products.

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?

'Only call after the person has agreed' gives an explicit precondition for invocation, and the consent parameter reinforces it. It does not name an alternative tool for the case where consent is absent, but the guidance is clear enough that an agent knows not to call it speculatively.

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