Skip to main content
Glama

define_signal

Define a CAN signal with bit-level precision, specifying start bit, length, and conversion parameters to map raw data to physical values.

Instructions

Define a named signal from a CAN message (bit-level precision). Physical value = (raw * scale) + offset.

Args: name: Signal name, e.g. 'engine_rpm' or 'throttle_pct'. can_id: CAN message ID. start_bit: LSB position (little_endian) or MSB position (big_endian), 0-based. length: Signal width in bits. byte_order: 'little_endian' (Intel/LSB-first) or 'big_endian' (Motorola/MSB-first). value_type: 'unsigned' or 'signed'. scale: Multiplier for raw→physical conversion. offset: Addend for raw→physical conversion. unit: Physical unit string, e.g. 'rpm', 'km/h', '%', '°C'. description: Human-readable description.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
can_idYes
start_bitYes
lengthYes
byte_orderNolittle_endian
value_typeNounsigned
scaleNo
offsetNo
unitNo
descriptionNo
Behavior2/5

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

No annotations provided, so description must cover behavioral traits. It explains what the tool does but does not disclose side effects (e.g., whether it creates, updates, or validates), persistence, or required state (e.g., established connection).

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?

The description is front-loaded with a one-line summary and formula, followed by a tidy list of parameter explanations. Every sentence is informative and none are superfluous.

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

Completeness4/5

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

The tool has 10 parameters, no output schema, and no schema descriptions. The description fully explains the purpose, conversion, and all parameters. However, it could briefly mention return value or success indication for completeness.

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

Parameters5/5

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

The description provides detailed explanations for all 10 parameters (e.g., name, start_bit, length, byte_order, value_type, scale, offset, unit, description). Since schema descriptions are absent (0% coverage), this adds essential meaning beyond the schema.

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 clearly states 'Define a named signal from a CAN message (bit-level precision)' and includes the conversion formula. It distinguishes from sibling tools like remove_signal or list_signals by specifying creation/definition.

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 guidance on when to use this tool versus alternatives like import_dbc or track_signal. The description does not mention prerequisites or context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/harrisonfaulkner/canbus-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server