Skip to main content
Glama
Sign In

Laso Finance

by finance.laso
OverviewDiscussionsAdmin

get_saved_cards

Read-onlyIdempotent

List the holder's saved cards

Lists the cards the account holder saved themselves: a card they already own, typed once on the card issuer's page and locked behind their passkey. Nothing is issued or prefunded, and no identity verification is needed. Every purchase paid with a saved card is approved by the holder on their own device.

The response carries display fields only, never a card number. An empty cards list means nothing is saved yet: call POST /create-saved-card-link and send the returned url to your human.

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
noteNoThe next step.
cardsNo
blockerNoPresent only when the holder finished saving a card but it is not readable yet. `needs_code`: they saved it on a card account they already had, and confirm it once with a one-time code in the dashboard. `linked_elsewhere`: the card account they unlocked is linked to another Laso account. Relay `note`; sending another link does not help with `needs_code`. One of: needs_code, linked_elsewhere.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / blocker
      Added value: +{
+  "description": "Present only when the holder finished saving a card but it is not readable yet. `needs_code`: they saved it on a card account they already had, and confirm it once with a one-time code in the dashboard. `linked_elsewhere`: the card account they unlocked is linked to another Laso account. Relay `note`; sending another link does not help with `needs_code`. One of: needs_code, linked_elsewhere.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world, but the description adds meaningfully beyond them: no card is issued or prefunded, no identity verification is required, purchases are approved by the holder on their device, and the payload never contains a card number. That last point is critical safety context for an agent handling payment data.

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?

Front-loaded with the core action, then semantics, then response shape and next step — a logical order with no filler sentences. It runs three short paragraphs where two would do, and the bolded 'Nothing is issued or prefunded' clause is slightly promotional, but every line carries information.

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, annotated, output-schema-bearing read tool, the description covers the remaining unknowns: what a saved card actually is, that no verification or issuance occurs, that numbers are absent from the response, how to read an empty list, and what to do next. Nothing an agent needs to call and interpret it 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?

The tool takes zero parameters, so there is no parameter surface for the description to clarify; baseline 4 applies. Nothing in the text misrepresents or invents inputs.

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?

Specific verb+resource ('List the holder's saved cards') and immediately disambiguates the resource from sibling concepts: these are cards the holder already owns, typed once at the issuer and passkey-locked, not newly issued cards. This separates it cleanly from order_card, create_reloadable_card, and get_card_data.

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?

Gives explicit downstream routing for the empty-result case ('call POST /create-saved-card-link and send the returned url to your human'), which is genuine when-to-act guidance. It does not, however, state when to prefer this over other read tools such as get_card_data or list_card_transactions, so the routing is one-directional rather than a full use/avoid statement.

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