Skip to main content
Glama

sebbi.pro - the proof layer for AI

Open an account

sebbi_create_account

Opens a sebbi.pro account and returns the API key. Only call after showing sebbi_terms and the person agreeing; pass the terms_version they agreed to and customer_agreed=true. The agreement is sealed into the chain. Free for 7 days.

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>",
      "terms_version": "<terms_version>",
      "customer_agreed": "<customer_agreed>"
    },
    "name": "sebbi_create_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
emailYes
companyNo
devicesNoEstimated devices; billing uses the real count
productNo
terms_versionYesterms_version from sebbi_terms
customer_agreedYestrue only if the customer read the terms and said yes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations (readOnly=false, openWorld=true, idempotent=false), it discloses three things an agent could not otherwise know: the response contains a secret API key, the agreement is immutably 'sealed into the chain,' and there is a 7-day free window. It does not say what happens on a duplicate email or a re-call, 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 tight sentences with the purpose, precondition, and post-condition front-loaded in that order. Every sentence carries operational weight; nothing is redundant with the title or annotations.

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?

With no output schema, the description usefully states that an API key is returned, and it covers the required legal fields and billing framing. The gaps are edge-case behavior (duplicate account, failed agreement) and the meaning of the product enum, which matter for a non-idempotent creation 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 coverage is 43%, so the description must compensate, and it does explain the semantics of terms_version and customer_agreed. However, the optional parameters (product enum values, devices estimate, company, name) get no coverage in either the description or most of the schema, leaving half the surface undocumented.

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?

The description opens with a specific verb and resource ('Opens a sebbi.pro account') and states the return value ('returns the API key'). It is clearly distinguishable from sibling tools like sebbi_terms or sebbi_billing_link because it names the account-creation action and its prerequisite.

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?

It gives an explicit gating condition: 'Only call after showing sebbi_terms and the person agreeing,' and names the sibling to invoke first. It also specifies the required call shape ('pass the terms_version they agreed to and customer_agreed=true'), leaving nothing to inference.

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