Skip to main content
Glama

embedded-eda

ieee754_inspect

Inspect IEEE-754 single (float32) and double (float64) sign, exponent, mantissa bits, hex representations, and subnormal/NaN/Inf edge states.

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": "ieee754_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
bitsNo
textNo
valueNoDecimal number (e.g. "3.14159", "-0.15625", "NaN") or 0x hex pattern.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses coverage of edge states like subnormal, NaN, and Inf, but does not state that the operation is read-only/no-side-effect or explain malformed-input handling or precedence among the optional inputs.

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 front-loaded sentence with no filler. It states the domain, supported widths, inspected fields, and edge cases efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with three optional inputs, ambiguous text/value semantics, no output schema, and no annotations, the description is incomplete for correct invocation. It explains output scope but not how the inputs combine or which should be supplied.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%, and the description does not compensate adequately. It maps 32/64 to single/double and references hex representations, but it leaves the text parameter and the relationship between text and value undocumented.

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 gives a specific verb (Inspect) and resource (IEEE-754 single and double floats), then enumerates exactly what is exposed: sign, exponent, mantissa bits, hex representations, and subnormal/NaN/Inf states. This is far more specific than a restatement of the tool name.

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

Usage Guidelines2/5

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

The description says what the tool does but gives no guidance on when to choose it over alternatives such as intel_hex_inspect or other decode/inspection siblings. There are no excluded cases or prerequisites, so usage selection is left entirely implicit.

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