Skip to main content
Glama
Sign In
x402-weblens-mcp

x402-weblens-mcp

by bartenderthiago82
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

CSV to typed JSON ($0.002)

weblens_csv_to_json

Convert CSV text into JSON rows with snake_case keys and detected column types, including integer, number, boolean, date, datetime, and string; delimiter is auto-detected.

Instructions

Convert CSV text to JSON rows with snake_case keys and a detected type per column (integer, number, boolean, date, datetime, string). Delimiter is auto-detected. Costs $0.002 USDC.

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": {
      "csv": "<csv>"
    },
    "name": "weblens_csv_to_json"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvYesCSV text
headerNoFirst row is the header (default true)
delimiterNoOptional delimiter

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does add real value by disclosing the price ($0.002 USDC), the type inference behavior, and delimiter auto-detection, but it says nothing about failure behavior on malformed CSV, how payment is transacted, or what a partially-typed column yields.

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?

Three short sentences, front-loaded with the conversion and its output shape, followed by the delimiter default and the price. Nothing is repeated from the schema and no sentence is wasted.

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

Completeness4/5

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

For a simple three-parameter transform with no output schema, the description covers the return shape (JSON rows, snake_case keys, per-column types), the default delimiter behavior, and the cost. It stops short of error semantics, which is the main remaining gap for a paid tool.

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 description coverage is 100%, so all three parameters are already documented, including the header default and the optional single-character delimiter. The description adds only the inference that delimiter detection is automatic when the parameter is omitted, which is marginal over the schema baseline.

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 names a specific verb and resource (convert CSV text to JSON rows) and adds concrete output characteristics: snake_case keys and a detected type per column with the type list enumerated. It is clearly distinct from repair-oriented siblings like weblens_json_repair, but it does not explicitly contrast itself with any named sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is only implied by the input requirement ('CSV text'), with no statement of when to choose this over weblens_json_repair or weblens_extract, and no preconditions such as input size or malformed-input handling. The cost note gives a practical reason to prefer it only for small inputs, but that guidance is not stated.

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