Skip to main content
Glama

Join the Protoship waitlist

join_waitlist

Puts your user on the Protoship waitlist for ordering PCBs, 3D prints, CNC parts and sheet metal through their agent. Protoship sends one email to confirm the address, later one with the invite. No newsletter. Use only your user's own email address and only with their consent. Privacy policy: https://protoship.dev/privacy

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

Input Schema

NameRequiredDescriptionDefault
emailYesYour user's email address.
deviceNoWhat your user wants to build, in a sentence. Optional.
interestsNoWhat your user wants to order. Optional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / device / description
      Previous value: -"The device your user wants to build, in a sentence. Optional."New value: +"What your user wants to build, in a sentence. Optional."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and destructiveHint=false, so the write-to-external-service nature is known. The description goes further by disclosing the concrete side effect — exactly two emails (address confirmation, then invite) and no newsletter — which is the kind of third-party-visible behavior an agent needs before acting. It stops short of saying what happens on a repeated submission, which matters given idempotentHint=false.

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?

Purpose is front-loaded in the first clause, followed by side-effect disclosure, then the consent constraint and privacy URL. Nearly every sentence earns its place, though the enumeration of orderable categories and the trailing privacy link make it slightly longer than strictly necessary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool that writes an external record, the description covers side effects, consent requirements and privacy, and with no output schema it need not explain return values. The remaining gap is repeat-call behavior: with idempotentHint=false and destructiveHint=false, an agent cannot tell whether a second call duplicates the waitlist entry or is rejected.

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 email, device and interests parameters are already fully documented, establishing a baseline of 3. The description adds real meaning for the required parameter by restricting it to the user's own address with consent, but says nothing about device or interests beyond the schema, so nothing pushes this above baseline.

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 ("Puts your user on the Protoship waitlist") and scopes it to ordering PCBs, 3D prints, CNC parts and sheet metal through Protoship's agent. None of the siblings (check_project, estimate_build, match_parts, request_finish, request_status) do anything similar, so an agent can route here without ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description gives a hard precondition ("Use only your user's own email address and only with their consent"), which is genuinely useful before calling. However, it never states when this tool is preferred over the sibling tools or which situations should not lead to a waitlist join, leaving the selection logic implied by the tool's purpose alone.

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