Skip to main content
Glama

Check a design value against a datasheet's rules

datasheetvend_check_design_value
Read-onlyIdempotent

Check one design value against every rule DatasheetVend extracted from a datasheet (its pin-cautions rulebook): for example a 4.7 kΩ pull-up, a 100 nF decoupling capacitor or a 3.6 V supply. Returns pass, fail or needs_review per rule that applies, with the rule's datasheet source, and a summary that counts EVERY rule, including the ones that could not be compared, so 0 failures never hides 'nothing was compared'. An unknown unit is refused, not passed. Pass the job_id of an extraction in your account that ran the pin_cautions module. Deterministic: runs DatasheetVend's checks in code, calls no model and extracts nothing. Costs no credits. Needs a DatasheetVend API key.

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": {
      "job_id": "<job_id>",
      "value": "<value>",
      "unit": "<unit>"
    },
    "name": "datasheetvend_check_design_value"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitYesIts unit, for example 'kohm', 'nF', 'V', 'mA'. An unrecognised unit is refused.
valueYesThe design value to check, for example 4.7
job_idYesAn extraction job in your account that ran the pin_cautions module.
packageNoThe package the design uses (for example 'TQFP32'), so package-specific rules apply.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already cover readOnly, idempotent, non-destructive and closed-world, and the description adds real behavior beyond that: pass/fail/needs_review per rule with datasheet source, a summary counting every rule including incomparable ones, unknown units refused rather than passed, deterministic code with no model calls, zero credit cost, and an API key requirement. That is strong disclosure of outcomes and cost, though return shape detail (ordering, format) remains implicit with no output schema. Since the annotations carry the safety profile, a 3 acknowledges the added context without over-crediting.

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?

Front-loaded with what the tool does and what it returns, then prerequisites, then cost/auth facts; every sentence carries operational information. Slight redundancy — the unrecognised-unit refusal appears both in the description and in the unit schema field — keeps it just short of a 5.

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?

For a tool with no output schema, the description supplies the return contract (pass/fail/needs_review per rule plus source and an all-rules summary), the key anti-false-confidence property (0 failures does not mean nothing was compared), the input prerequisite, and cost/auth expectations. An agent has everything needed to call it correctly and interpret results.

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 100%, so a baseline of 3 applies, but the description goes further by pairing value and unit in examples and stressing that an unrecognised unit is refused rather than coerced to a pass — meaningful semantics for the most error-prone input. The optional package parameter, which controls package-specific rule matching, is left entirely to the schema, so it is not a full 5.

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 and resource (check one design value against every pin-cautions rule extracted from a datasheet) and pins the scope to a single value rather than a whole design, which separates it from compatibility/netlist-check siblings. Concrete examples (4.7 kΩ pull-up, 100 nF decoupling cap, 3.6 V supply) make the input domain unmistakable.

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?

Gives a clear precondition: the job_id must come from an extraction that ran the pin_cautions module, which effectively routes the agent to extract_pin_cautions first. It does not explicitly name an alternative check tool or state when NOT to use this one, so it stops short of full when/when-not guidance.

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