Skip to main content
Glama

Laso Finance

by finance.laso
OverviewDiscussionsAdmin

get_version

Get the current docs version

Returns the current 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

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and handles it well: it states the call is free, requires no auth or payment header, returns a cacheable content-hash version, and explains the relationship to response headers and the API catalog. No side effects or hidden requirements are left ambiguous.

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 with the core purpose in the first sentence and is organized into logical paragraphs: return value/auth, cache-freshness guidance, and catalog integration. It is slightly verbose for a zero-parameter endpoint, especially the RFC 9727 and Link-header details, but each paragraph contributes meaningful context for an agent deciding when and why to call it.

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 no output schema, the description covers everything an agent needs: what is returned, the specific files involved, cost/auth implications, the stale-cache detection workflow, and an alternative way to obtain the same version from response headers. Nothing required to invoke it correctly 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 has zero parameters and 100% schema coverage, so the baseline is 4. The description adds useful meaning by explaining that the version is a content-hash over a fixed set of documentation files rather than a user-facing release number, which clarifies what the returned value represents.

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 the current docs version' and clarifies it is the content-hash version of the Laso Finance agent docs, listing the exact files covered. This clearly separates it from the many get_* sibling tools by identifying a distinct, concrete deliverable.

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 concrete use case: agents aggressively cache docs, so call this to detect a stale cache when the last-seen docs_version differs. It also mentions that every API response carries the value in the X-Laso-Docs-Version header, providing a context-aware alternative source, though it does not explicitly state when-not-to-call the tool.

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