Skip to main content
Glama
Sign In
lithtrix-mcp

lithtrix-mcp

Official
by lithtrix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

lithtrix_blob_list

Retrieve a paginated list of blob metadata using optional page and per_page parameters. Requires API key authentication.

Instructions

List blob metadata (GET /v1/blobs). Optional page and per_page. Requires LITHTRIX_API_KEY.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "lithtrix_blob_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage (default 1)
per_pageNoPage size (1–100, default 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 mentions the HTTP method and required API key, but does not explicitly state it is read-only or describe side effects. It is adequate but lacks depth.

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?

Extremely concise: one sentence with the core action and a separate sentence for a prerequisite. No filler, front-loaded.

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 exists, and the description does not explain the return format or metadata fields. For a list operation, this is a significant gap.

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 has 100% description coverage, so the schema already fully documents the parameters. The description simply restates they are optional, adding no new meaning beyond the schema.

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 clearly states it lists blob metadata with optional pagination. It uses the verb 'list' and specifies the endpoint, making the purpose clear. However, it doesn't explicitly distinguish from sibling tools like 'lithtrix_blob_search' or '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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives (e.g., search, meta). The description does not mention use cases, prerequisites, or when not to use it.

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