Skip to main content
Glama
Sign In
circuit-agent

circuit-agent

by mo9652962-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

calculate_stencil_aperture_ratios

Read-onlyIdempotent

Evaluate SMT stencil aperture area and aspect ratios per IPC-7525 to flag paste-release-deficient apertures and prevent print defects.

Instructions

Evaluate SMT stencil aperture area ratio (>= 0.66 laser-cut) and aspect ratio (>= 1.5) compliance per IPC-7525 Stencil Design Guidelines, identifying paste-release-deficient apertures.

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": {
      "apertures": "<apertures>"
    },
    "name": "calculate_stencil_aperture_ratios"
  }
}

Input Schema

NameRequiredDescriptionDefault
aperturesYesList of apertures ({ref, shape: 'rect'|'circle', width_mm, length_mm}).
min_area_ratioNoMinimum acceptable area ratio (default: 0.66).
min_aspect_ratioNoMinimum acceptable aspect ratio (default: 1.5).
foil_thickness_umNoStencil foil thickness in μm (default: 100).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.7

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so safety is covered. The description adds useful domain context (the IPC-7525 criteria and what a failure means), but with no output schema it never says what the response contains or how deficiencies are reported.

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?

A single dense sentence with the standard and thresholds front-loaded and zero filler; every clause carries meaning.

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 read-only calculation tool with full schema coverage, the description supplies the standard, thresholds, and the purpose of the result. The main gap is that no output schema exists and the description does not describe the returned structure, keeping it below a 5.

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%, including the aperture object shape and all three numeric defaults, so the schema carries the parameter burden. The description restates the default thresholds but adds no format or unit guidance beyond what the schema already provides.

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?

States a specific verb (Evaluate), the exact resource (SMT stencil aperture area ratio and aspect ratio compliance), and the governing standard (IPC-7525). It also names the outcome (identifying paste-release-deficient apertures), which distinguishes it from neighbors like calculate_solder_paste_volume.

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?

The description makes the use case clear: checking aperture designs against the >=0.66 area-ratio and >=1.5 aspect-ratio rules to find paste-release problems. It gives no explicit when-not guidance or named alternative tool, so it stops short of a 5.

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