Skip to main content
Glama
Sign In
ecu-harness

ecu-harness

by omaratif1995
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Explain a definition

ecu_describe
Read-onlyIdempotent

Check an AUTOSAR container kind or parameter's type, range, allowed values, required status, and children before adding containers or setting values you are unsure about in ARXML.

Instructions

What a container kind or parameter allows: type, range, allowed values, required, children. Check before adding containers or setting values you are unsure about.

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_describe"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoDefinition name or path, e.g. ComSignal or Com/ComConfig/ComSignal.
pathNoOr: path of an existing container; describes its kind.
filterNoOnly parameters whose name contains this text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is fully covered structure-side. The description adds real value by enumerating the information returned (type, range, allowed values, required, children), which substitutes for the absent output schema. Beyond that it says nothing about cost, caching, or behavior when a name is unresolvable.

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 sentences, the returned-attribute list is front-loaded and the usage instruction follows it, with no filler. The style is telegraphic ('What a container kind or parameter allows: ...') which is efficient but slightly clipped relative to a full sentence.

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?

For a zero-required-parameter, read-only introspection tool with no output schema and no nested objects, the definition covers the essentials: what it inspects, what it returns, and when to reach for it. Only minor gaps remain — behavior on unknown names and any contrast with other read tools.

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 three parameters are documented in the schema itself, including the kind-vs-path alternative and the filter substring semantics. The description's phrase 'container kind or parameter' loosely mirrors the two lookup modes but adds no syntax, format, or precedence detail beyond the schema. 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?

The description names the resource (a container kind or parameter definition) and enumerates what it reports: type, range, allowed values, required, children. Combined with the title 'Explain a definition', an agent can tell this is a schema-introspection tool rather than a value getter like ecu_get. It stops short of explicitly contrasting itself with the other read-side siblings (ecu_get, ecu_find, ecu_overview).

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

Usage Guidelines4/5

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

It gives concrete, actionable timing guidance — 'Check before adding containers or setting values you are unsure about' — which ties the tool to a specific preceding action in the edit workflow. It does not name the mutation sibling (ecu_edit) or state when this is unnecessary, so it falls short of the explicit when/when-not/alternatives bar.

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