Skip to main content
Glama
Sign In
qianxing-dev-mcp

qianxing-dev-mcp

by nasodaengineer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_nodes

List API nodes by category, side, or prefix to quickly find relevant endpoints for development tasks.

Instructions

按 category / side / prefix 列出节点名，便于发现 API

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": "list_nodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
sideNo
limitNo
prefixNo名称前缀或包含
categoryNo分类关键词，如 事件节点 / 执行节点

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are present, so the description carries the full burden. It indicates a read-only listing operation but does not disclose pagination, response format, authorization needs, or any side effects. The minimal description leaves behavioral expectations vague.

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?

The description is a single concise sentence that front-loads the core action and filtering dimensions. Every word earns its place, with no redundancy or extraneous detail.

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?

With no annotations, no output schema, and a 4-parameter tool, the description is too sparse. It omits return format, pagination behavior, and any caveats about the 'side' or 'category' values. An agent would lack essential context to correctly invoke and interpret the result.

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 50% (only prefix and category have descriptions). The description mentions category, side, and prefix as filtering criteria, adding context for those parameters, but does not address the limit parameter. It partially compensates for the missing schema descriptions but not fully.

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 the tool lists node names and specifies the filtering dimensions (category, side, prefix), giving a specific verb and resource. It does not explicitly distinguish from the sibling lookup_node, but the act of listing vs looking up a single node is implied, so it is clear but lacks explicit differentiation.

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 is provided on when to use this tool versus alternatives like lookup_node. The description only states what it does, not when it should be preferred, nor does it mention any exclusions or prerequisites.

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