Skip to main content
Glama

firmware_inspect

Read-only

Read Intel HEX files and validate checksums, memory addresses, segment overlap, and reset vectors to catch firmware image errors before flashing or simulation.

Instructions

Read Intel HEX and validate checksums, addresses, overlap and reset vector.

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": {
      "path": "<path>"
    },
    "name": "firmware_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is settled externally. The description adds real value by enumerating what is validated (checksums, addresses, overlap, reset vector), but never says what happens on invalid input or how results are surfaced.

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?

One sentence with the action front-loaded and the validation targets listed compactly; no filler. It is arguably too terse, but nothing in it is wasted.

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?

With no output schema, the description would ideally say whether validation failures are returned as a report or raised as an error, and what the input path must point to. It covers the read-and-check scope adequately but leaves the result shape and input requirements unstated.

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 0% for the sole parameter, so the description carries the full burden for "path" — yet it never mentions the parameter, its expected file type, path format, or whether relative paths are allowed. The 'Intel HEX' phrasing implies a .hex file but does not define the input.

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?

"Read Intel HEX and validate checksums, addresses, overlap and reset vector" gives a specific verb (read + validate) and a specific resource (Intel HEX firmware files), plus the exact checks performed. It implicitly separates itself from firmware_build, but doesn't name any sibling or state the relationship.

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?

No when-to-use, when-not-to-use, or alternative is mentioned. The agent must infer that this is the inspection counterpart to firmware_build from the name alone.

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