Skip to main content
Glama

set_part_fields

Update a library part's supplier, MPN, manufacturer, or description without changing its pins or footprint; null clears a field, and verified parts are rejected.

Instructions

Set a library part's suppliers, mpn, manufacturer or description; pins and footprint stay. null removes one. A verified part is refused.

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": {
      "id": "<id>"
    },
    "name": "set_part_fields"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
mpnNo
suppliersNoe.g. { "lcsc": "C6186" }; null removes one
descriptionNo
manufacturerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/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 usefully discloses that only metadata fields change, that pins and footprint stay, that null clears a value, and that verified parts are refused, but it omits return behavior, permission requirements, and whether suppliers are replaced or merged.

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 compact and front-loaded, with each clause adding distinct information. It avoids filler and states the core action, unaffected fields, null behavior, and refusal condition efficiently.

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?

For a mutation tool with a nested suppliers object and no annotations or output schema, the description covers key constraints but leaves important operational details unspecified. It is adequate for basic invocation but not fully complete regarding replacement semantics, errors, and responses.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is low at 20%, but the description names all four settable fields and explains null semantics. It still does not explain the required id parameter, expected mpn/manufacturer formats, or whether the suppliers object replaces or merges existing mappings.

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 uses a specific verb (Set) and resource (library part fields: suppliers, mpn, manufacturer, description), and explicitly states that pins and footprint are unaffected. This distinguishes it from broad part-creation or part-info tools.

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

Usage Guidelines4/5

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

It gives clear usage context, including that null removes a field and that a verified part is refused. It does not name alternatives such as part_info or create_part, but the supported fields and refusal condition make the intended use clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.