Skip to main content
Glama

join_waitlist

Idempotent

Join the free Human Test Desk optional pilot-updates list. Only submit an email with its owner’s permission to receive pilot updates. Requires explicit consent true. No login, payment, or test booking. Idempotent by email; emails are not verified.

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
emailYes
consentYes
interestNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations cover the safety profile (destructiveHint=false, openWorldHint=false, idempotentHint=true), so the bar is lower, yet the description still adds meaningful context: idempotency is keyed on email specifically, emails are not verified, and no account/payment is required. The only redundancy is restating idempotency, which the annotation already declares.

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, front-loaded sentences with no filler, and the core action leads. There is mild duplication between 'Only submit an email with its owner's permission' and 'Requires explicit consent true', which are near-restatements of the same condition.

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 3-parameter write tool with no output schema, the description covers the essential contract: consent requirement, idempotency key, no auth/payment, and unverified emails. It is only missing what occurs on a duplicate or invalid submission and any mention of the interest field.

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 description coverage is 0%, so the description must carry param meaning. It explains email (owner permission required) and consent (must be explicitly true), adding real value over the schema's const/format hints, but the optional 'interest' parameter (maxLength 500) is never mentioned in description or schema.

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?

States a concrete verb+resource ('Join the ... pilot-updates list') and explicitly rules out adjacent behavior ('No login, payment, or test booking'), which helps separate it from request_test. It stops short of naming the other test-related siblings (get_test, cancel_test), so differentiation from the full family is only partial.

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?

Gives usable preconditions: submit only with the email owner's permission, and consent must be true. It also states exclusion conditions (no login, payment, or test booking), though it never names an alternative tool to use instead, so routing is implied rather than prescribed.

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