Skip to main content
Glama

QDev

Join the QDev email list

join_email_list
Idempotent

Starts a sign-up to QDev's email list for a person who asked to join. QDev emails that address a confirmation link, and the address joins the list only when its owner opens the email and presses Confirm. Before calling, show the person this text and get their yes: "One email when each product opens and when an event is announced, and nothing else. Every one has a one-click unsubscribe link. Sent by QDev Inc., 675 Sturdivant Drive, Clarksville, TN 37042, info@quantumdev.io. Privacy Policy: https://quantumdev.io/privacy/#email-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>",
      "agreed": "<agreed>"
    },
    "name": "join_email_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesThe person's own email address.
agreedYesTrue only when the person has been shown the text in this tool's description and has said yes to it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already indicate a write/open-world operation, but the description adds important behavior: QDev sends a confirmation link, and the address joins only after the owner presses Confirm. It also discloses the exact consent language required before calling, making the double opt-in flow clear.

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?

The description is front-loaded with purpose, then explains confirmation behavior, then gives the required pre-call action with the consent script. The long consent block is necessary and therefore earns its place; there is no filler.

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?

For a two-parameter external signup tool with no output schema, the definition covers the consent precondition, double opt-in side effect, and what happens after the call. Although it does not describe return values or edge cases like already-subscribed addresses, the critical invocation context is present.

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?

Schema coverage is 100%, and the schema already defines email as the person's own address and agreed as consent. The description adds the actual consent text that the agreed parameter depends on, which is essential operational meaning beyond the schema, though it adds little about email formatting.

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 action and resource: 'Starts a sign-up to QDev's email list' for a person who asked to join. This is clearly a join/mutation tool, distinct from the list/search/fetch siblings, and its purpose 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly limits use to a person who asked to join and mandates pre-call steps: show the exact consent text and get their yes. The 'person who asked' condition also implies not to use it for unsolicited sign-ups.

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