Skip to main content
Glama

Create a flayr account (agent)

agent_signup

[writes flayr data · write scope] Creates a flayr account for an AI agent, no key or browser needed: sends a 6-digit code to email (an inbox you read, e.g. AgentMail). Calling it accepts the flayr Terms of Service and Privacy Policy for the account. Every agent account starts on the Free plan. If the address already has a flayr account, the same call is how an agent logs in: agent_signup_verify then returns a capped key on that account. (Wraps POST /api/v2/agent-signup.)

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>",
      "agentName": "<agentName>",
      "intendedUse": "<intendedUse>"
    },
    "name": "agent_signup"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesFormat: Email string; e.g. "person@example.com". The agent's own inbox; the code is sent here.
agentNameYesFormat: string; e.g. "Content Assistant". Name of the agent creating the account.
ownerEmailNoFormat: Email string; e.g. "person@example.com". The human who answers for the agent (may be required by flayr's abuse settings).
intendedUseYesFormat: string; e.g. "Example". What the agent will use flayr for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / agentName / description
      Added value: +"Format: string; e.g. \"Content Assistant\". Name of the agent creating the account."
    • changedInput schema / properties / email / description
      Previous value: -"The agent's own inbox; the code is sent here."New value: +"Format: Email string; e.g. \"person@example.com\". The agent's own inbox; the code is sent here."
    • changedInput schema / properties / intendedUse / description
      Previous value: -"What the agent will use flayr for."New value: +"Format: string; e.g. \"Example\". What the agent will use flayr for."
    • changedInput schema / properties / ownerEmail / description
      Previous value: -"The human who answers for the agent (may be required by flayr's abuse settings)."New value: +"Format: Email string; e.g. \"person@example.com\". The human who answers for the agent (may be required by flayr's abuse settings)."
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false), and the description goes further: it discloses the emailed 6-digit code, that the call constitutes acceptance of the Terms of Service and Privacy Policy, that accounts start on the Free plan, the existing-account/login behavior, and the underlying endpoint (POST /api/v2/agent-signup). The one gap is what this call itself returns (only the verify step's capped key is described).

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-loaded with a tagged scope marker and the core verb+resource, then the mechanics, then the alternate login reading, then the endpoint. Dense but every sentence carries information; the parenthetical endpoint note is the only marginally expendable element.

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 4-parameter creation tool with no output schema, the description covers prerequisites (readable inbox), side effects (ToS acceptance, Free plan), and the follow-up step. The only shortfall is that it never says what agent_signup returns immediately after the code is dispatched.

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 each field documents its format and example, so the schema already carries the parameter load. The description adds one useful nuance, that `email` must be an inbox the agent can actually read (e.g. AgentMail), but says nothing additional about `agentName`, `ownerEmail`, or `intendedUse`, leaving the baseline of 3 appropriate.

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 ('Creates a flayr account for an AI agent') plus the key mechanic ('no key or browser needed: sends a 6-digit code to email'). It also explicitly distinguishes the sibling step agent_signup_verify, so an agent can tell the two apart without inspecting 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 the condition for use in both directions: new addresses create an account, and an address that already has an account means the same call is the login path, followed by agent_signup_verify. That is explicit when-to-use and next-step routing rather than implied guidance.

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