can-engineering-mcp

Overview Schema Source Related Servers Discussions Admin

inspect_database_summary

Summarizes a DBC database: protocol type, baudrate, ECU, message and signal counts, and the node matrix. Use it to size up a CAN or CAN FD file before deeper inspection.

Instructions

Protocol type, baudrate, ECU/message/signal counts, and node matrix.

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": {
      "dbc_path": "<dbc_path>"
    },
    "name": "inspect_database_summary"
  }
}

Input Schema

Name	Required	Description	Default
`dbc_path`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 3, 2026

TDQS

C2.6/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the shape of the return payload (protocol type, baudrate, counts, node matrix), which is genuine behavioral value with no output schema present, but it never states that the operation is a read-only inspection with no side effects, nor how errors on a bad path are handled.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Very short with no wasted words, but it is an unstructured fragment rather than a sentence with a lead clause, and its brevity comes at the cost of under-specification rather than efficiency.

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 one-parameter tool with no annotations and no output schema, the description omits the parameter meaning, usage context, and read-only guarantee, leaving only a list of returned fields. It is not sufficient for an agent to call the tool confidently without inspecting the schema.

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 single required parameter dbc_path, and the description never mentions the path, its format, or whether it is a filesystem path or identifier. The description does nothing to compensate for the undocumented parameter.

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

Purpose3/5

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

The description is a noun phrase listing returned data ('Protocol type, baudrate, ECU/message/signal counts, and node matrix') rather than a verb+resource statement. An agent can infer this summarizes a DBC file's metadata, and it is distinguishable from siblings like validate_database_integrity or search_database, but the purpose is implied rather than stated.

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 guidance at all. With 18 siblings including search_database and validate_database_integrity, there is no indication of when a summary is preferable to searching or validating, and no prerequisites (e.g., file must exist) are mentioned.

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