Skip to main content
Glama

Laso Finance

by finance.laso
OverviewDiscussionsAdmin

search_docs

Read-onlyIdempotent

Search the Laso Finance agent docs (SKILL.md and the full API reference). Returns the most relevant sections. Use this for anything the tool descriptions don't answer: auth flows, funding, fees, webhooks, error handling.

Input Schema

NameRequiredDescriptionDefault
queryYesSearch terms, e.g. fund managed wallet, or: gift card fees.

Output Schema

NameRequiredDescriptionDefault
noteNoWhere to read the full docs when nothing matched.
resultsNoBest-matching doc sections, most relevant first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "note": {
+      "description": "Where to read the full docs when nothing matched.",
+      "type": "string"
+    },
+    "results": {
+      "description": "Best-matching doc sections, most relevant first.",
+      "items": {
+        "properties": {
+          "content": {
+            "description": "Section text, truncated to 2500 characters.",
+            "type": "string"
+          },
+          "heading": {
+            "description": "Section heading.",
+            "type": "string"
+          },
+          "source": {
+            "description": "Document the section came from.",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "note": {
-      "description": "Where to read the full docs when nothing matched.",
-      "type": "string"
-    },
-    "results": {
-      "description": "Best-matching doc sections, most relevant first.",
-      "items": {
-        "properties": {
-          "content": {
-            "description": "Section text, truncated to 2500 characters.",
-            "type": "string"
-          },
-          "heading": {
-            "description": "Section heading.",
-            "type": "string"
-          },
-          "source": {
-            "description": "Document the section came from.",
-            "type": "string"
-          }
-        },
-        "type": "object"
-      },
-      "type": "array"
-    }
-  },
-  "type": "object"
-}New value: +null
  3. First observed

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description need not repeat that. The description adds the scope of the search (SKILL.md and API reference) and that it returns sections, which is useful context but not substantial behavioral disclosure beyond annotations.

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?

Three sentences, front-loaded with the core purpose, then output, then usage guidance. No wasted words.

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 single-parameter read-only search tool with an output schema, the description covers purpose, usage context, and scope. It is complete enough for an agent to decide when and how to invoke it.

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?

The input schema fully documents the query parameter with examples. The description adds no additional parameter semantics, but with 100% schema coverage the baseline of 3 is appropriate.

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 searches the Laso Finance agent docs, specifically SKILL.md and the full API reference, and returns the most relevant sections. This is a specific verb and resource that distinguishes it from sibling search tools like search_gift_cards and search_merchants.

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?

Explicitly states when to use: 'for anything the tool descriptions don't answer', with examples like auth flows, funding, fees, webhooks, and error handling. This provides clear decision guidance for agents.

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