Skip to main content
Glama

register_agent

Get an agent_key instantly — no website needed. Creates a LicenseSaaS account (buyer, seller or both) for this email and emails the owner a sign-in link. If the email already has an account, ask the owner for a key from Account settings -> Agent keys.

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

Input Schema

NameRequiredDescriptionDefault
nameYesPerson or company name shown to others.
roleNoWhat the account does on LicenseSaaS (default buyer).
emailYesThe owner's email, e.g. "ann@acme.com". They get a sign-in link and can revoke the key.
company_nameNoCompany name, if different from name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / company_name / description
      Added value: +"Company name, if different from name."
    • addedInput schema / properties / email / description
      Added value: +"The owner's email, e.g. \"ann@acme.com\". They get a sign-in link and can revoke the key."
    • addedInput schema / properties / role / description
      Added value: +"What the account does on LicenseSaaS (default buyer)."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare the mutating, non-idempotent, open-world profile, and the description adds the concrete consequences: an account is created, the owner is emailed a sign-in link, and the owner can revoke the key. What is left unstated is what a second call with an already-registered email actually returns (error vs. new key), 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the outcome ('Get an agent_key instantly') before the mechanics and the existing-account caveat. No repetition or filler; each sentence carries distinct information.

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 registration tool with no output schema, the description covers who is affected (owner email), the side effect (email sent, key issued), and the duplicate-account path. The remaining gap is the return value and the exact behavior on repeat calls for the same email.

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 every parameter including the role enum and its default is already documented. The description only echoes role as 'buyer, seller or both' and ties email to the sign-in link — meaning already present in the schema — and adds nothing about name vs. company_name.

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 LicenseSaaS account (buyer/seller/both) for a given email and issues an agent_key. No sibling tool does account registration, and the description makes that uniqueness obvious by naming the account/key outcome rather than a generic 'register' action.

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?

Explicitly handles the main edge case: if the email already has an account, stop and ask the owner for a key from Account settings -> Agent keys. That is a real when-not condition with a fallback, though the fallback is a manual UI path rather than a sibling tool, so routing within the toolset is only implied.

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