Skip to main content
Glama

Laso Finance

by finance.laso
OverviewDiscussionsAdmin

get_auth_link

Read-onlyIdempotent

Get a login link for the web dashboard

Returns a URL that a human can open in a browser to log in to the Laso Finance web dashboard as the authenticated user. Useful for humans who want to see what their AI agent has been doing (view cards, transactions, balances, etc.).

The URL carries a short single-use login code rather than a long token, so relay it to your human verbatim; it passes through tool-output credential filters intact. Do not fetch or open the URL yourself: redeeming the code consumes the human's login.

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
user_idNoThe authenticated user's ID (wallet address)
auth_urlNoURL to open in a browser to log in to the Laso Finance dashboard. Carries a short single-use login code.
expires_inNoSeconds until the login code expires

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / auth_token
      Removed value: -{
-  "description": "Laso credential. Only if the MCP connection has no Authorization header.",
-  "type": "string"
-}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "auth_url": {
+      "description": "URL to open in a browser to log in to the Laso Finance dashboard. Carries a short single-use login code.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "expires_in": {
+      "description": "Seconds until the login code expires",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "user_id": {
+      "description": "The authenticated user's ID (wallet address)",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "auth_url": {
-      "description": "URL to open in a browser to log in to the Laso Finance dashboard. Carries a short single-use login code.",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "expires_in": {
-      "description": "Seconds until the login code expires",
-      "type": [
-        "number",
-        "null"
-      ]
-    },
-    "user_id": {
-      "description": "The authenticated user's ID (wallet address)",
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint, idempotentHint, destructiveHint), the description discloses critical behavioral details: the URL carries a short single-use login code, it passes through credential filters intact, and fetching/opening the URL would consume the human's login. This is exactly the kind of non-obvious behavior an agent needs to know.

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?

The description is front-loaded with the core purpose in the first sentence, then adds essential usage and security context. Every sentence earns its place: return value, use case, credential-filter behavior, and the explicit warning not to fetch the URL. No redundant or filler content.

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 zero-parameter tool with a rich annotation set and an output schema, the description covers everything an agent needs: what the tool returns, why it is useful, how to relay the URL, and a critical behavioral warning. There are no meaningful 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?

The tool takes zero parameters, so parameter semantics are trivially satisfied. The description correctly adds no parameter-specific details because none exist; the baseline of 4 applies given the empty schema.

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: 'Get a login link for the web dashboard.' It clearly distinguishes this from sibling tools like get_kyc_link by specifying that the link logs the human into the Laso Finance web dashboard as the authenticated user, and it states the purpose ('see what their AI agent has been doing').

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 gives a clear use case: 'Useful for humans who want to see what their AI agent has been doing (view cards, transactions, balances, etc.).' It does not explicitly name alternative tools or state when not to use it, but the context is unambiguous enough for an agent to select this tool appropriately.

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