Skip to main content
Glama

build-get_starter

Generate starter build files for a new Exeris application: a pom.xml or package.json pre-wired with annotation processors, codegen goals and tested dependency versions.

Instructions

Return the build files for a NEW Exeris application and write none: for 'backend', a pom.xml whose parent is exeris-app-parent and which depends on exeris-app-starter; for 'frontend', a package.json with @exeris/codegen-ts and its exeris-gen generate script; for 'both', the two under backend/ and frontend/. Ask this BEFORE hand-writing a pom.xml or package.json for an Exeris application: the starter already wires the annotation processor, the codegen goals and the dependency set. Every version comes from the exeris-app-bom the bridge was released with, which names one tested tooling + kernel + SDK triple; the tool reports it as bomVersion and triple. supplied lists what the application still adds itself, starting with the JDBC driver. Needs no project: it reads bundled data only, and you write the files with your own tools.

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": {
      "variant": "<variant>"
    },
    "name": "build-get_starter"
  }
}

Input Schema

NameRequiredDescriptionDefault
variantYesWhich application to start: 'backend' (Maven), 'frontend' (npm), or 'both' (a backend and a frontend that generates from the backend's build).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

A4.6/5.0
Behavior5/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 and does: it states the tool writes nothing, needs no project, reads bundled data only, and that the caller writes files with its own tools. It also discloses provenance behaviour (all versions come from the exeris-app-bom the bridge was released with, reported as bomVersion and triple) and that `supplied` lists what the application still adds, starting with the JDBC driver.

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?

It is a single dense paragraph, but it is front-loaded with the outcome and the per-variant results, then the when-to-use rule, then provenance. A few clauses (the annotation-processor rationale, the 'supplied' aside) are secondary but still earn their place; some splitting into shorter sentences would aid scanning.

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

Completeness5/5

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

There is no output schema, yet the description explains the returned payload (build files per variant, bomVersion, triple, supplied) and the constraints on invocation (no project needed, nothing written). For a one-parameter, read-only lookup tool, nothing an agent needs to call it correctly is missing.

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?

Schema coverage is 100% and the enum values are already documented, so the baseline is 3. The description adds real meaning beyond the schema by tying each variant to concrete output artefacts and, for 'both', explaining that the frontend generates from the backend's build.

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 opens with a specific verb and resource ('Return the build files for a NEW Exeris application') and immediately narrows scope by naming the exact artefacts per variant (pom.xml with exeris-app-parent, package.json with @exeris/codegen-ts). 'write none' plus the explicit list of generated files separates it cleanly from any generation or mutation tool in the sibling set.

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 an explicit trigger condition: 'Ask this BEFORE hand-writing a pom.xml or package.json for an Exeris application', with a stated rationale (the starter already wires the annotation processor, codegen goals and dependency set). It does not name a catalog alternative to use instead in any situation, but the pre-condition is unusually clear.

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