Skip to main content
Glama
Sign In
lithtrix-mcp

lithtrix-mcp

Official
by lithtrix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

lithtrix_blob_signed_url

Generate a time-limited HTTPS read URL for a blob. Anyone with the URL can access the data until the expiry time.

Instructions

Mint a time-limited HTTPS read URL for a blob (GET /v1/blobs/{blob_id}/signed-url). Anyone with the URL can GET bytes until expiry — share carefully. Requires LITHTRIX_API_KEY.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "blob_id": "<blob_id>"
    },
    "name": "lithtrix_blob_signed_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
blob_idYesContent-addressed blob id (b_ + 16 hex chars)
expires_inNoTTL seconds (min 60; max from server). Omit for API default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It discloses time-limited access and authentication requirement (LITHTRIX_API_KEY), but omits details like whether the URL is revocable, whether it counts towards rate limits, or if it leaves any trace.

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?

Two sentences, front-loaded with the core action, no redundant words. Every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, and description does not mention the return value (a signed URL string). For a tool that outputs a URL, this is a significant gap. It also lacks guidance on error cases or URL format.

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 has 100% coverage with clear parameter descriptions. Description adds context like 'time-limited' and 'Omit for API default' for expires_in, enhancing understanding beyond schema.

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?

Description uses specific verb 'Mint' and identifies the resource 'time-limited HTTPS read URL for a blob'. It includes the HTTP method and endpoint, clearly differentiating from siblings like lithtrix_blob_download and lithtrix_blob_meta.

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?

Explicitly states that anyone with the URL can GET bytes until expiry and advises caution, implying the tool is for temporary sharing. However, it does not explicitly say when not to use it or name alternative tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools