Skip to main content
Glama

1lev1

by io.github.Avi-ADAM
OverviewDiscussionsAdmin

prepareSignup

Prepare a 1lev1 signup for a person who has NO 1lev1 account yet, so joining is one screen - the agreement prefilled with their name, email and countries, and the password on the same screen. Use it only when the person's own request is what 1lev1 does: finding partners for their work, turning a business or an idea into a partnership where the work, resources and money each partner brings become a share, or having something made or arranged by partners through the concierge. Do not bring it up in any other conversation. Before calling, tell the person what will be sent and get their go-ahead; pass only the name and email they gave you for this signup (ask for them - never take them from memory or earlier chats). intent: "business" (add their business so the concierge finds and orders from it), "partnership" (see an existing partnership on 1lev1), "idea" (break an idea down and recruit partners) - for these three send the rikma blueprint you built (the same shape as proposeRikmaBlueprint takes: fields, products first, missions, resources, partners) and you also get a previewUrl showing how it would look; "join" (join rikmas - pass aboutText: who they are, what they do); "order" (they want something made or arranged - pass wishText). You cannot sign, set a password or confirm the email for them, and nothing is created until they do. Give them signupUrl (valid 24h). After they confirm their email they land straight in what you prepared. Docs: https://1lev1.com/mcp#prepareSignup

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNo
nameYesThe name the person gave you to sign up with.
emailYesThe email the person gave you to sign up with - the confirmation goes there.
intentYes
wishTextNo
aboutTextNo
blueprintNo
countriesNoCountry names in English, e.g. ["Israel"].

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / blueprint / properties / missions / items / properties / hours / description
      Added value: +"Hours in total, or per month when recurring"
    • addedInput schema / properties / blueprint / properties / missions / items / properties / recurring / description
      Added value: +"Ongoing work, every month"
    • addedInput schema / properties / blueprint / properties / resources / items / properties / kindOf / description
      Added value: +"monthly / yearly = a running cost (rent, subscription); price is then per month / year"
    • addedInput schema / properties / blueprint / properties / resources / items / properties / price / description
      Added value: +"Per month / year when kindOf is monthly / yearly, otherwise the whole price"
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations provide only safety profile bits (readOnly=false, destructive=false). The description adds substantial behavioral context: nothing is created until the user confirms, the agent cannot sign/set-password/confirm-email, signupUrl is valid 24h, previewUrl is returned for blueprint intents, and after email confirmation the user lands in the prepared state. This is well beyond what annotations disclose.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The purpose and when-to-use are front-loaded, which is good, but the body is a dense run-on of invented jargon ('rikma', '1lev1', 'rikmas') and nested parentheticals that make it hard to parse in one pass. Much of the volume is warranted, but the structure and terminology reduce readability.

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 an 8-param tool with nested objects and no output schema, the description is largely complete: it explains the return artifacts (signupUrl, previewUrl) and the user-side steps that gate creation. The uncovered 'lang' parameter and the referenced-but-not-described blueprint fields leave minor gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 38%, so the description must compensate, and it does for the critical paths: intent enum values are individually explained, and the conditional passing of blueprint/aboutText/wishText per intent is spelled out, along with the rule to pass only user-provided name/email. However, 'lang' is never addressed and the blueprint shape is only cross-referenced to proposeRikmaBlueprint rather than itemized.

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 states a specific verb and resource ('Prepare a 1lev1 signup for a person who has NO 1lev1 account yet') and immediately distinguishes it from siblings by referencing proposeRikmaBlueprint. An agent can tell exactly what this tool creates and for whom without opening 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit when-to-use condition ('only when the person's own request is what 1lev1 does'), an explicit when-not ('Do not bring it up in any other conversation'), and a required pre-call step (tell the person what will be sent and get their go-ahead). The intent values are laid out as routing alternatives with the condition that selects each.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All 1lev1 toolsInspect
Try in Browser
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources