Skip to main content
Glama

Laso Finance

by finance.laso
OverviewDiscussionsAdmin

get_signup_status

Wait for your human to finish the signup

Long-polls until the human opens the claim link and finishes creating the account. Holds the connection open for about 60 seconds and returns 204 No Content if they have not finished yet.

Retry on 204 and nothing else. The call already blocks for you, so add no sleep between attempts. Every other status is final and retrying will not change the answer: 401 means the token is wrong, 410 means the link expired. Both carry "terminal": true in the body. A loop written as "retry until 200" spins at network speed against those, because they answer instantly rather than holding the connection.

On completion it returns your api_key — delivered exactly once. Store it before doing anything else; a later poll returns the account without it. By that point the human is on their dashboard, their agent wallet is provisioned, and you are already recorded as their connected agent, so announceAgentConnection is not needed on this path.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
claim_codeYesThe claim_code from the same POST /signup response.
claim_tokenYesThe claim_token from POST /signup.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "api_key": {
-      "description": "Your lasoak_ key. Delivered EXACTLY ONCE — null on any later poll.",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "api_key_note": {
-      "description": "Present only when api_key is null, explaining that it was already delivered.",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "auth": {
-      "description": "An id_token / refresh_token bundle you can use immediately.",
-      "type": [
-        "object",
-        "null"
-      ]
-    },
-    "callable_base_url": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "next_steps": {
-      "items": {
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "type": [
-        "array",
-        "null"
-      ]
-    },
-    "status": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "user_id": {
-      "description": "The Laso user id of the new account.",
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations provided, the description takes full burden. It discloses the ~60s hold, the 204 timeout, the terminal statuses with 'terminal': true in the body, the api_key delivered exactly once, and the fact that subsequent polls omit it. This is exceptionally transparent about behavior and edge cases.

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 multi-paragraph and fairly long, but every section adds critical operational detail: retry semantics, terminal codes, api_key delivery, and the announceAgentConnection note. It is front-loaded with the main purpose and uses bold and bullet-like formatting for emphasis, making it scannable despite length.

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?

For a long-polling tool with no output schema, the description covers all necessary context: return values (204, api_key, terminal statuses), retry loop behavior, and downstream implications (wallet provisioned, agent recorded). Nothing an agent needs to call it correctly is missing.

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% and both parameters are well-described in the schema (claim_token and claim_code from POST /signup). The description only restates 'the same POST /signup response' without adding new meaning, so it stays at the baseline.

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 'Wait for your human to finish the signup' and then explains it long-polls until the account is created. It specifies the resource (signup status), the action (long-poll), and the outcome (returns api_key). This clearly distinguishes it from sibling tools like start_signup or get_auth_link.

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?

The description provides explicit retry guidance: 'Retry on 204 and nothing else' and explains that 401 and 410 are terminal. It also notes that announceAgentConnection is not needed on this path, implying when it would be. It does not name specific sibling alternatives, but the context is clear enough for an agent to decide when to use this tool.

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