Skip to main content
Glama

Laso Finance

by finance.laso
OverviewDiscussionsAdmin

get_version

Read-onlyIdempotent

Get the current docs version

Returns the current API contract version (api_version), the versioning and deprecation policy, and the content-hash version of the Laso Finance agent docs (SKILL.md, openapi.json, llms.txt, llms-full.txt, ai-plugin.json). Free, no auth or payment header.

Agents aggressively cache these docs, so use this to detect a stale cache: if the docs_version you last saw differs from the value returned here, refetch the docs. Every API response also carries this value in the X-Laso-Docs-Version response header, alongside X-Laso-Docs-Manifest, which points at the authoritative freshness beacon at https://laso.finance/.well-known/docs-version.json.

This route is also the status target of the API catalog at https://laso.finance/.well-known/api-catalog (RFC 9727), which every response advertises via a Link header with rel="api-catalog".

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
docsNoPer-file entries, each with a `url` and a stable `sha256` content identifier. Compare against the values you last saw to tell which file changed.
noteNo
versioningNoThe versioning and deprecation policy in machine-readable form: which header carries the version, what counts as an additive versus a breaking change, and how a retirement is signalled.
api_versionNoVersion of the API contract itself (this description's `info.version`). Moves only on a breaking change, unlike `docs_version`. Also sent on every response as `X-Laso-Api-Version`.
docs_versionNo12-character content hash of the agent docs. Changes only when the docs change.
api_catalog_urlNoURL of the RFC 9727 API catalog (`application/linkset+json`) indexing the OpenAPI description, the agent docs, and this status route.
docs_manifest_urlNoURL of the authoritative freshness beacon, served with no-cache.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / api_version
      Added value: +{
+  "description": "Version of the API contract itself (this description's `info.version`). Moves only on a breaking change, unlike `docs_version`. Also sent on every response as `X-Laso-Api-Version`.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedOutput schema / properties / versioning
      Added value: +{
+  "description": "The versioning and deprecation policy in machine-readable form: which header carries the version, what counts as an additive versus a breaking change, and how a retirement is signalled.",
+  "type": [
+    "object",
+    "null"
+  ]
+}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "api_catalog_url": {
+      "description": "URL of the RFC 9727 API catalog (`application/linkset+json`) indexing the OpenAPI description, the agent docs, and this status route.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "docs": {
+      "description": "Per-file entries, each with a `url` and a stable `sha256` content identifier. Compare against the values you last saw to tell which file changed.",
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "docs_manifest_url": {
+      "description": "URL of the authoritative freshness beacon, served with no-cache.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "docs_version": {
+      "description": "12-character content hash of the agent docs. Changes only when the docs change.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "note": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "api_catalog_url": {
-      "description": "URL of the RFC 9727 API catalog (`application/linkset+json`) indexing the OpenAPI description, the agent docs, and this status route.",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "docs": {
-      "description": "Per-file entries, each with a `url` and a stable `sha256` content identifier. Compare against the values you last saw to tell which file changed.",
-      "type": [
-        "object",
-        "null"
-      ]
-    },
-    "docs_manifest_url": {
-      "description": "URL of the authoritative freshness beacon, served with no-cache.",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "docs_version": {
-      "description": "12-character content hash of the agent docs. Changes only when the docs change.",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "note": {
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null
  4. First observed

TDQS

A4.3/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 behavior, but the description goes further: it declares the endpoint is free, needs no auth or payment header, explains aggressive client-side caching, and documents the response header and freshness beacon. This is rich context beyond structured fields.

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 front-loaded: purpose first, then return contents, usage, and supporting headers. It is longer than strictly necessary for a zero-param tool, and the final paragraph about RFC 9727 API catalog and Link header is tangential, but no sentence is confusing or out of order.

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?

With an output schema present, the description need not enumerate return values, yet it still explains api_version, versioning policy, and docs_version clearly. Combined with explicit auth and cache-detection guidance, an agent has everything needed to call this tool correctly.

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 the schema is empty and schema coverage is 100%. Per the rubric, zero parameters sets a baseline of 4; there is nothing to clarify or compensate for.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource ('Get the current docs version') and details exactly what version data is returned. It never names a sibling or differentiates itself from tools like search_docs, so it stops short of the top score.

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?

It explicitly states when to call it ('use this to detect a stale cache') and gives the triggering condition (docs_version differs from last seen). It also points to the X-Laso-Docs-Version header as an equivalent mechanism, though it never states when not to call it or how it relates to the sibling search_docs.

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