Skip to main content
Glama
Sign In
lithtrix-mcp

lithtrix-mcp

Official
by lithtrix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

lithtrix_blob_delete

Soft-delete a blob by providing its content-addressed blob ID. Requires a valid LITHTRIX_API_KEY for authorization.

Instructions

Soft-delete a blob (DELETE /v1/blobs/{blob_id}). 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_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
blob_idYesContent-addressed blob id (b_ + 16 hex chars)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

The description mentions 'soft-delete' and requires an API key, but does not explain the implications of soft-delete (e.g., reversibility, side effects, or what happens to the blob). With no annotations, the description carries full burden for behavioral disclosure, and it falls short.

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, no fluff, front-loaded with the action and immediate requirement.

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

Completeness3/5

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

Adequate for a simple delete tool with one parameter, but lacks details on soft-delete behavior and response format. With no output schema, the description could be more informative.

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?

Schema coverage is 100% and the schema's description is already clear; the tool description adds no extra meaning beyond what the schema provides.

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 'Soft-delete a blob' with the HTTP method and path, which is specific and distinguishes it from sibling blob tools like download, list, etc.

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 vs alternatives; it does not mention when a soft-delete is appropriate or any prerequisites beyond the API key.

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