Skip to main content
Glama

beta_signup

Idempotent

Put a user on the beta notification list: one email when anything about early access changes. Ask before calling: it records the address they give you. Re-signing the same address is safe (status already_recorded). Someone who needs a higher rate limit today should get a free key with research_access: it is issued instantly.

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

Input Schema

NameRequiredDescriptionDefault
orgNoLab, company or institution (optional).
emailYesThe user's email address.
sourceNoWhere the signup came from, e.g. mcp (optional).
use_caseNoWhat they would use the API for (optional). No patient details.

Output Schema

NameRequiredDescriptionDefault
okYesAlways true; a rejected signup comes back as an error result.
statusYesalready_recorded: the address was already on the list. Both are success — do not retry.
messageYesWhat to tell the user, including how to get a beta key today.
releaseYesIPD-IMGT/HLA release every verdict was computed against.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / use_case / description
      Previous value: -"What they would use the API for (optional)."New value: +"What they would use the API for (optional). No patient details."
  2. Added

TDQS

A4.5/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing a side effect (one notification email on early-access changes), a data-capture/consent obligation, and the concrete repeat-call outcome (status already_recorded), which makes the idempotentHint meaningful rather than abstract. It stops short of covering failure modes or rate/volume limits, so it is strong rather than complete.

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?

Three sentences, each carrying distinct information: purpose, consent prerequisite, idempotency guarantee, and alternative routing. Purpose and scope are front-loaded with 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?

An output schema exists, so return values need no explanation, and the description still supplies the one return value that matters operationally (already_recorded). Purpose, consent, idempotency, and the sibling alternative are all present for a four-parameter mutation tool.

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 100%, so the schema already explains email, org, source, and use_case, and the description adds nothing field-specific beyond implying the email is stored. Baseline 3 applies when the schema does the parameter work.

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 ("Put a user on the beta notification list") and immediately scopes the effect ("one email when anything about early access changes"). It also names a sibling, research_access, and the different need it serves, so an agent can discriminate without opening either schema.

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?

Gives an explicit precondition ("Ask before calling: it records the address they give you") and an explicit routing rule for the alternative path ("Someone who needs a higher rate limit today should get a free key with research_access"). Both when-to-use and when-to-use-something-else are covered.

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.