Skip to main content
Glama
Sign In
ecu-harness

ecu-harness

by omaratif1995
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Project overview

ecu_overview
Read-onlyIdempotent

Start here to inspect modules, the tool driver, and the open change in an ARXML configuration before editing, so you know what to review and modify.

Instructions

Start here: modules, tool driver, open change.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered structurally. The description adds only the shape of the payload (modules, tool driver, open change) and says nothing about scope, freshness, or size of that overview. Credit is modest given the low bar annotations set.

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?

Eight words, front-loaded with the actionable 'Start here' before the content list — no padding. It loses a point only because the compressed noun phrases are cryptic rather than efficient.

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 must convey what comes back, and it does so only as three unexplained nouns; an agent cannot predict the structure or depth of the overview. For a simple, zero-argument read tool the essentials (call it first, it is read-only) are present, but the payoff is under-described.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline applies and there is nothing for the description to disambiguate. No parameter-related claims are made or needed.

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 name and title already say 'project overview', and the description adds a content hint: modules, tool driver, open change. But the verb is implied rather than stated, and the noun list is terse jargon ('tool driver', 'open change') an agent cannot fully resolve without calling it. It reads as an entry-point summary, but the purpose is only partially pinned down.

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?

'Start here:' is an explicit directive about when to call it — first, before other tools. No exclusions or named alternatives are given, which is acceptable for an overview tool but leaves nothing to distinguish follow-up sequencing beyond the opening word.

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