Skip to main content
Glama

Laso Finance

by finance.laso
OverviewDiscussionsAdmin

refresh_card_data

Trigger a card data refresh

Requests an updated balance for a card.

For U.S. non-reloadable cards (default), the card is re-scraped from the issuer via a retrieval queue and processed asynchronously. Rate limited per card to one request every 5 minutes, and to at most 12 refreshes in any rolling 24-hour period.

For international non-reloadable cards, a balance update request is recorded; an admin will manually update the balance within 24 hours. While a balance update is already pending for a card, additional requests for that card return 409.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
card_idYesThe card ID to refresh data for
card_typeNoThe type of card. Defaults to `Non-Reloadable U.S.` if omitted.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageNo
successNo

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": {
+    "message": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "success": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "message": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "success": {
-      "type": [
-        "boolean",
-        "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=false, destructiveHint=false), the description discloses async processing, rate limits (5-minute and 12 per 24h), manual handling for international cards, and the 409 conflict behavior. This gives the agent a clear picture of side effects and failure modes without contradiction.

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 concise, front-loaded with the purpose, and structured into clear paragraphs for U.S. and international behavior. Every sentence adds value, with no redundancy or filler.

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?

The description covers the action, parameters, rate limits, error condition, and async behavior. An output schema is present, so return values are covered. For a refresh tool with this complexity, nothing essential is missing.

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 100%, so both parameters are documented. The description adds value by explaining the impact of card_type (defaulting to U.S., different processing paths) and the meaning of card_id in context, which goes beyond the schema's terse descriptions.

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 clearly states the tool triggers a card data refresh and requests an updated balance. It distinguishes itself from siblings like get_card_data by focusing on the refresh action, and the title and description align with the resource and action.

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 explains when to use the tool: to refresh card data, and it differentiates behavior for U.S. vs international cards, including rate limits and async processing. It also notes the 409 error when a refresh is already pending. However, it doesn't explicitly contrast with get_card_data or other alternatives, leaving some inference needed.

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