Skip to main content
Glama
Sign In
ecu-harness

ecu-harness

by omaratif1995
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Search the configuration

ecu_find
Read-onlyIdempotent

Search AUTOSAR ECU configuration ARXML containers by name, kind, parameter value, or reference relation, returning paths for other tools; add 'show' to include parameter values and answer questions in one call.

Instructions

Search containers by name, kind, parameter value or reference relation. Returns paths for the other tools; 'show' adds parameter values to each result, so one call can answer a question.

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

Input Schema

NameRequiredDescriptionDefault
kindNoContainer kind (definition name), e.g. ComSignal.
showNoParameter names to include in each result, comma-separated.
limitNoMaximum results, default 20.
paramNoOnly containers that set this parameter or reference.
queryNoText that the short name must contain.
scopeNoconfig = ECUC containers (default); definitions = parameter definitions; all = every named element of all loaded ARXML files.
underNoOnly search below this path.
valueNoWith param: only containers where it has this value.
offsetNoSkip this many results (paging).
users_ofNoPath: only the containers that refer to this container.
targets_ofNoPath: only the containers that this container refers to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, closed-world behavior, so safety is covered. The description adds that results are paths usable by other tools and that 'show' enriches each hit with parameter values, but omits result capping/paging behavior (limit default 20, offset) which matters for broad queries.

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?

Two tight sentences, front-loaded with the search axes before the enrichment advice. "so one call can answer a question" is slightly elliptical but does justify the 'show' parameter.

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 11 optional parameters and no output schema, the description should do more to describe the shape of returned results — it says "paths" but not what a result record contains beyond that. It is adequate for a read-only search but leaves result format and broad-query behavior underspecified.

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 100%, so all 11 parameters including scope's enum and the param/value pairing are already documented. The description reinforces 'show' and the reference-relation axes but adds no syntax or format detail beyond the schema, so baseline 3 applies.

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?

Specific verb (search) plus resource (containers) and enumerates the search axes: name, kind, parameter value, reference relation. It does not explicitly contrast with ecu_get or ecu_describe, so an agent must infer that this is the lookup that feeds them.

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?

The phrase "Returns paths for the other tools" implies this is the entry point for downstream calls, and the 'show' clause implies when to enrich results in one call. But there is no explicit when-not guidance or direct contrast with sibling lookups such as ecu_get/ecu_describe.

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

Deploy Server

Other Tools