Skip to main content
Glama

Estimate a land pattern (IPC-7351-style, generic)

datasheetvend_calculate_land_pattern
Read-onlyIdempotent

Estimate a land pattern from package numbers: a generic IPC-7351-style pad width, pad length and courtyard for a perimeter package (QFN/DFN/SON leadless, or QFP/SOIC/SSOP/TSSOP/SOP gull-wing). This is a nominal estimate, NOT IPC-7351B's tolerance-stacked tables, NOT IPC-certified and NOT the datasheet's recommended land pattern: use the datasheet's own drawing when it prints one. It gives one pad size for every pad, no pad positions, no numbered pad map and no exposed (thermal) pad, so it cannot build a footprint on its own; for an official KiCad footprint use datasheetvend_match_kicad_footprint. Each value's origin is in inputs_used (given, derived from a standard outline, estimated from pitch, or formula), and caveats travel with every result. An unsupported family or a missing input is refused and named. Free, no API key, no model call, reads no account data.

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": {
      "package_type": "<package_type>",
      "pin_count": "<pin_count>",
      "body_width_mm": "<body_width_mm>",
      "body_length_mm": "<body_length_mm>",
      "pitch_mm": "<pitch_mm>"
    },
    "name": "datasheetvend_calculate_land_pattern"
  }
}

Input Schema

NameRequiredDescriptionDefault
pitch_mmYesTerminal pitch, in millimetres
pin_countYesNumber of terminals. Only checked to be above 0.
span_x_mmNoLead-tip span across the width (gull-wing only; give both spans or neither), in millimetres
span_y_mmNoLead-tip span across the length (gull-wing only; give both spans or neither), in millimetres
package_typeYesPackage name as the datasheet prints it, for example 'QFN', 'LQFP', 'TSSOP', 'SOIC'.
pad_width_mmNoA pad width to use as given instead of the 60%-of-pitch estimate, in millimetres
body_width_mmYesBody width, in millimetres
density_levelNoMargin level: most (largest pads), nominal (default) or least. Nominal margins, not IPC levels A/B/C.
pad_length_mmNoA pad length to use as given instead of the formula, in millimetres
body_length_mmYesBody length, in millimetres

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive, closed-world), the description discloses the most important behavioral limits: values are nominal rather than tolerance-stacked, one pad size for all pads with no pad positions or thermal pad, provenance of each value in inputs_used, and caveats attached to every result. It also confirms no authentication, no cost, no model call and no account data access.

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?

The block is long but front-loaded with the core purpose and each subsequent sentence carries distinct information (limits, alternatives, provenance, refusal, cost). A little density could be trimmed, particularly the closing trust sentence, but there is no filler or repetition.

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?

With no output schema, the description still covers what comes back (pad dimensions, courtyard, per-value origin in inputs_used, caveats) and how failures appear (refused and named). For a 10-parameter estimation tool with full schema coverage and annotations, nothing an agent needs to call it correctly is missing.

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 description coverage is 100%, so the baseline is 3; the description still adds meaning by explaining that pad_width_mm and pad_length_mm override a default 60%-of-pitch estimate and formula, and that density_level uses nominal margins rather than IPC levels A/B/C. It does not, however, explain the gull-wing span_x/span_y pairing rule beyond what the schema already states.

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 (estimate) and resource (land pattern) plus the exact outputs: pad width, pad length and courtyard, for named package families (QFN/DFN/SON, QFP/SOIC/SSOP/TSSOP/SOP). It also delineates scope negatively (not IPC-7351B tables, not certified, not the datasheet's own pattern) and names a sibling for a different need, so an agent can separate it from datasheetvend_match_kicad_footprint without reading schemas.

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?

Explicit routing is given: use this for a nominal generic estimate, prefer the datasheet's own drawing when it prints one, and use datasheetvend_match_kicad_footprint when an official KiCad footprint is wanted. It even specifies refusal behaviour for unsupported families or missing inputs, so both the when-to-use and when-not-to-use conditions are covered.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources