Skip to main content
Glama

Verify agent sign-up

agent_signup_verify

[writes flayr data · write scope] Checks the emailed code and returns an API key (shown once). New address: the new account's first key (account: "new"). Address that already has a flayr account: a NEW key on that account, capped at read + write (account: "existing"); the account holder and every organization owner/admin get email and in-app notices plus a dashboard banner and can revoke it, and accounts with SSO or with "Allow agent login" off refuse (403). Reconnect to this MCP server with Authorization: Bearer <apiKey>. (Wraps POST /api/v2/agent-signup/verify.)

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

Input Schema

NameRequiredDescriptionDefault
codeYesFormat: string; e.g. "123456". Six-digit verification code emailed to the account owner.
emailYesFormat: Email string; e.g. "person@example.com". Email address.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / code / description
      Added value: +"Format: string; e.g. \"123456\". Six-digit verification code emailed to the account owner."
    • addedInput schema / properties / email / description
      Added value: +"Format: Email string; e.g. \"person@example.com\". Email address."
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations: the key is shown only once, new vs. existing accounts produce different account values, existing accounts are capped at read + write, owners/admins get email, in-app, and dashboard notifications and can revoke, and certain accounts are refused with 403. For a non-idempotent, non-read-only call this is exactly the disclosure an agent needs.

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?

Front-loads the action and result, then the new-vs-existing branches, then the reconnect instruction, with zero filler. It is dense and packed into one paragraph with a trailing parenthetical, which makes it harder to scan than a short bulleted branch structure would be.

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?

There is no output schema, and the description still explains the return value (an API key, shown once) and the meaning of the `account` field values. Combined with the 403 refusal cases and revocation behavior, an agent can act on this without consulting anything else.

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% and both parameters are already documented with format, pattern, and examples. The description adds no syntax or format meaning for `email` or `code` beyond what the schema supplies, so the baseline of 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 ('Checks the emailed code') and the concrete outcome ('returns an API key (shown once)'), plus the underlying endpoint. It is clearly the second step of sign-up, distinct from the initiation step a sibling would perform, without needing to open the schema.

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?

Implies the prerequisite (a six-digit code was emailed) and prescribes the next step after success (reconnect with `Authorization: Bearer <apiKey>`). It also gives the precise refusal conditions (SSO enabled or 'Allow agent login' off → 403), but never explicitly says to call the initiating sign-up tool first, so the entry condition is inferred.

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