Skip to main content
Glama

Estimate supply current and battery life

datasheetvend_estimate_power_budget
Read-onlyIdempotent

Estimate a system's supply current and battery life (not thermal power dissipation) from parts your account extracted: total active current (mA), total standby current (uA), a breakdown per part and battery life on six standard batteries, as the DatasheetVend Workbench POWER tab computes it. Reads ONLY the jobs you pass: include each part's power_battery run, and its pinout run (it sets the role a fallback figure rests on). Active is the highest stated active row, standby the deepest stated low-power row (a best case), typical where stated and max otherwise. A part with no stated current gets a generic figure for its role, flagged is_estimated, and the totals then include estimates: read coverage (chips_active_stated of chips_on_bench, chips_standby_stated) before you repeat a number. Battery life assumes 5% active / 95% standby, nominal capacity, no derating or self-discharge. system_voltage_v is echoed, never used to rescale a current. A job whose outputs are gone is refused. 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_ids": "<job_ids>"
    },
    "name": "datasheetvend_estimate_power_budget"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idsYes1-12 extraction jobs in your account: each part's power_battery run, and its pinout run.
system_voltage_vNoThe bench supply rail, echoed in the answer (currents are not rescaled). Default 3.3.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, yet the description adds substantial behavior beyond them: how active and standby values are selected, what happens to parts lacking stated current (generic figure plus is_estimated flag), the coverage fields to check before quoting totals, the 5%/95% and nominal-capacity battery assumptions, refusal of purged jobs, determinism, and that it costs no credits.

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?

Purpose and the thermal exclusion are front-loaded, and the dense sentences carry real information about estimation rules and assumptions. A few statements duplicate the schema (the voltage echo, the battery assumptions repeated in spirit), and the long run-on phrasing makes it slower to parse than it needs to be.

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 tells the agent what comes back — total mA, total uA, per-part breakdown, battery life on six standard batteries, and the coverage counters — plus the exact computation rules, so an agent could call it and interpret the result correctly.

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 both parameters are already documented, but the description adds real meaning: job_ids must span a power_battery run plus the pinout run because pinout 'sets the role a fallback figure rests on,' and it stresses that system_voltage_v is only echoed. The voltage-echo claim largely restates the schema, limiting it below a 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?

The description opens with a specific verb and resource ('Estimate a system's supply current and battery life') and explicitly excludes the nearest false friend ('not thermal power dissipation'), so an agent can separate it from the thermal-limits and power-domains siblings without opening a schema.

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 concrete input prerequisites — 'include each part's power_battery run, and its pinout run' — and a failure condition ('A job whose outputs are gone is refused'), which is clear usage context. It never names an alternative tool or says when another estimator should be preferred, so it stops short of explicit routing.

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