Skip to main content
Glama
Sign In
ljs-mcp

ljs-mcp

by LJS-Y
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ljs_search

Searches LJS Vue3 plugins by scenario to confirm whether a ready-made implementation exists, covering tables, tree data, big-screen numbers, 3D carousels, large dropdowns, and utility functions.

Instructions

搜索 LJS 的 Vue3 插件。LJS 是作者自研的 7 个包，封装了表格、树形数据、时间轴、大屏数字、3D 轮播、大数据量下拉与常用工具函数。这些包的 API 命名与社区通用方案不同（例如格式化为 "万/亿"用的是 longNumText 而非自写逻辑），无法从通用知识推断，猜错参数会导致返工。

当方案涉及以下需求时，先搜索确认有无现成实现，避免重复造轮子：

  • 表格：动态列配置、导出 Excel、锁定列、多级表头

  • 树形数据：扁平数组转树、层级展示、菜单树

  • 大屏数字滚动、数据看板指标跳动

  • 时间轴、发展历程、蛇形时间线

  • 3D 球面轮播、立体标签云

  • 大数据量下拉、远程搜索下拉

  • 工具函数：日期/金额格式化、判空、字典、国密 SM2-SM4、水印、脱敏、WebSocket、MQTT、HTML 转 PDF

搜索成本很低：未命中会明确返回「未找到」并列出全部可用插件，不会让你误判。返回结果含匹配度与推荐理由，命中后用 ljs_read 拿完整用法、ljs_api 查准确签名。

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": {
      "query": "<query>"
    },
    "name": "ljs_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo返回结果条数，默认 3
queryYes自然语言描述需求，如「大屏数字要滚动增长」「表格列要能动态配置」

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and mostly discharges it: it discloses that a miss is non-ambiguous, that all available plugins are listed on no-match, and that results carry match scores and recommendation reasons. It does not discuss result count defaults or ranking mechanics in depth, but the failure mode and output shape are clear.

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?

Front-loaded with the core statement, then a scannable capability list, then the cost/follow-up note. The bulleted requirement list is long but each line maps to a real search target, so it earns its space; only slight trimming would be possible.

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?

There is no output schema, yet the description explains what comes back (match score, recommendation reason, full plugin list on a miss) and which sibling to call next. For a two-parameter search tool this leaves nothing an agent needs unresolved.

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%, so both parameters are already documented in the schema, including the natural-language framing of query and the default of 3 for limit. The description reinforces that query should be phrased as a need rather than an API name, but adds no syntax or format detail beyond the schema. Baseline 3 applies.

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?

Opens with a specific verb+resource ("搜索 LJS 的 Vue3 插件") and immediately scopes what LJS is: seven self-authored packages covering tables, tree data, timelines, big-screen numbers, 3D carousels, large dropdowns and utilities. It explicitly separates itself from siblings by stating that ljs_read gets full usage and ljs_api looks up exact signatures.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use trigger ("当方案涉及以下需求时，先搜索确认有无现成实现，避免重复造轮子") followed by a concrete requirement list, plus a when-not-to-worry clause: searching is cheap and a miss returns an explicit "未找到" with the full plugin list. It also names the follow-up tools to use after a hit.

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