Skip to main content
Glama

Laso Finance

by finance.laso
OverviewDiscussionsAdmin

start_signup

Start a signup for a human with no Laso account

Begins account creation for a human who does not have a Laso account yet. Requires no authentication, because the caller has no account.

This does not create the account. An agent cannot: the account is created by Privy in the human's own browser, so it belongs to them and not to their agent. What this returns is a claim_url to hand over.

Give your human the claim_url verbatim in your very next reply (send message_for_human if unsure what to say), and do not open it yourself. Then poll GET /signup-status, which holds the connection open until they finish and hands you your lasoak_ API key.

Rate limited per IP.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelNoOptional label recorded on the minted API key so your human can tell keys apart.
agent_nameNoYour name, shown to your human on the claim screen and recorded as the connected agent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "claim_code": {
-      "description": "The code inside claim_url. Pass it back to /signup-status alongside claim_token.",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "claim_token": {
-      "description": "Your receipt for this signup. Shown once; store it. Exchanged at /signup-status for your API key.",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "claim_url": {
-      "description": "Give this to your human verbatim. Never open it yourself.",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "expires_at": {
-      "description": "Epoch ms when the claim link expires.",
-      "type": [
-        "number",
-        "null"
-      ]
-    },
-    "expires_in": {
-      "description": "Seconds until the claim link expires (86400).",
-      "type": [
-        "number",
-        "null"
-      ]
-    },
-    "message_for_human": {
-      "description": "A ready-to-send reply containing the link. Send this as your next message.",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "next_steps": {
-      "items": {
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "type": [
-        "array",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations to lean on, the description fully carries behavioral disclosure. It states that no account is created, that Privy creates it in the human's browser, that ownership belongs to the human rather than the agent, that the endpoint is rate limited per IP, and that the status poll holds the connection open until completion. This is exceptionally transparent for an unannotated tool.

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?

The description is front-loaded with purpose and organized into clear paragraphs covering behavior, workflow, and rate limits. It is slightly redundant in the first two sentences both describing the signup start, but every sentence otherwise earns its place and the structure aids comprehension.

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?

Given no output schema and no annotations, this description is unusually complete: it covers purpose, auth requirements, side effects, return value, the exact handoff action, the follow-up polling tool, and the rate limit. An agent has everything needed to invoke it correctly and understand the unexpected non-creation behavior.

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 the baseline is 3. The description does not add new parameter-level detail about label or agent_name beyond what the schema already provides, though the mention of the returned lasoak_ API key subtly reinforces label's purpose.

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 opening line 'Start a signup for a human with no Laso account' states a specific verb, resource, and target user, and the description immediately clarifies what the tool is not: 'This does **not** create the account.' It is clearly distinguishable from siblings like get_signup_status, which it explicitly references as the polling follow-up.

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?

The description gives concrete when-to-use context: a human with no Laso account, and explicitly says 'Requires no authentication, because the caller has no account.' It also lays out a precise workflow: hand over the claim_url verbatim, do not open it yourself, then poll GET /signup-status, with a cross-reference to message_for_human for uncertain wording.

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

All Laso Finance toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources