Skip to main content
Glama

minia2a — hosted x402 API marketplace (HTTP)

x402-ohms-law-r

Ohms Law R: Computes resistance as voltage divided by current 🆓 5 free trial calls per signed wallet

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "x402-ohms-law-r"
  }
}

Input Schema

NameRequiredDescriptionDefault
currentNo
voltageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / current / description
      Removed value: -"Current to process"
    • removedInput schema / properties / voltage / description
      Removed value: -"Voltage to process"
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does add useful non-obvious context — the '5 free trial calls per signed wallet' note signals a pay-per-call x402 endpoint requiring a signed wallet — but it says nothing about return format, precision, or units.

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?

A single front-loaded sentence with the formula first, followed by the pricing caveat. No filler; the emoji/price tag is short and adds a real operational constraint.

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 trivial two-input calculator with no output schema, the description covers the computation but omits unit conventions and the shape of the returned resistance value — the two things an agent most needs to call and interpret it correctly.

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 0% and both parameters are untyped strings, so the description must compensate. It does map the two inputs to their physical roles ('voltage divided by current'), but never states expected units (volts/amps), numeric format, or whether the strings must be plain decimals.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource and the exact formula: 'Computes resistance as voltage divided by current.' This implicitly distinguishes it from siblings x402-ohms-law-i and x402-ohms-law-v, though it never names them explicitly.

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

Usage Guidelines3/5

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

Usage is only implied by the formula — an agent must infer that this is the tool to pick when the unknown is resistance. There is no explicit statement of when to use it vs. the two sibling Ohm's Law tools, and no prerequisites are given.

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.