pcb_create_equal_length
Create an equal-length group for specified nets to enforce matched routing lengths in PCB design.
Instructions
创建等长组
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | 等长组名称 | |
| nets | Yes | 网络名称列表 |
Create an equal-length group for specified nets to enforce matched routing lengths in PCB design.
创建等长组
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | 等长组名称 | |
| nets | Yes | 网络名称列表 |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It only states 'create' but does not disclose any behavioral traits (e.g., whether it modifies the board immediately, requires selections, or has side effects). The description adds no transparency beyond the name.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single phrase, which is concise, but it lacks any structural elements like bullet points or sections. It earns its place but does not provide enough value. A longer description would be justified given the tool's purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description is minimal for a tool that creates an equal length group. With no output schema and no annotations, the agent lacks information about return values, error conditions, or integration with other PCB tools. It is not complete enough for nuanced decision-making.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with descriptions in Chinese for both parameters. The description does not add additional meaning beyond the schema. Baseline score of 3 is appropriate as the schema already conveys parameter meaning.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The name and description clearly indicate that the tool creates an equal length group for nets, which distinguishes it from sibling tools like pcb_delete_equal_length or pcb_list_equal_lengths. The description is in Chinese but the verb 'create' and resource 'equal length group' are unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No usage guidance is provided. The description does not specify when to use this tool versus alternatives, such as creating a diff pair or manually constraining nets. There are no prerequisites or context for its use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/0xruth1ezz/jlc-eda-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server