Skip to main content
Glama
Sign In
carmaker-mcp

carmaker-mcp

by dimitr-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Times at which a quantity reaches values

cm_results_crossings
Read-only

Interpolate times when a result quantity crosses specified values, then read other quantities at each first crossing to derive lap, sector, or gate-based measurements.

Instructions

Interpolated times at which a quantity crosses each value, and the time between the first crossings of consecutive values (lap or sector times from distance gates); with at, the values of other quantities there (the speed at 75 m).

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": {
      "erg": "<erg>",
      "quantity": "<quantity>",
      "values": "<values>"
    },
    "name": "cm_results_crossings"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNoOther quantities to read at each first crossing, e.g. ['Car.v', 'Car.ax']
ergYesResult file (.erg): absolute path, or relative to the project
valuesYesValues to find, e.g. gate distances in m
quantityYese.g. 'Car.Distance' for gates along the course
directionNoWhich crossingsany

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real behavioral content: crossings are interpolated, consecutive first crossings are differenced to yield lap/sector times, and `at` performs a secondary read of other quantities at each first crossing. It omits edge behavior (value never crossed, direction default) and the response shape, though an output schema exists.

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?

A single sentence with the primary result (interpolated crossing times) front-loaded, followed by the derived interval behavior and the `at` modifier. Dense but free of filler; the nested parentheticals make it slightly harder to parse than a split structure would.

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?

With annotations covering safety, a fully documented schema and an output schema, the remaining burden on the description is conceptual semantics, which it covers well. The gaps are edge-case behavior for unmatched values and the default of `direction`, which are minor for a read-only analysis call.

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 coverage is 100%, so every parameter is already documented, establishing a baseline of 3. The description reinforces the intent of `values` (gate distances) and `at` (cross-quantity reads, e.g. speed at 75 m) but adds no syntax or format detail beyond what the schema states, and says nothing about `direction` or `erg`.

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?

States a precise computation: interpolated times at which a quantity crosses given values, plus intervals between first crossings of consecutive values. That is a specific verb+resource with scope. It does not name any sibling (e.g. cm_results_read or cm_results_plot) to disambiguate the results family, so it stops short of a 5.

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?

Usage is only implied through the examples (distance gates, lap or sector times), so an agent can infer the intended scenario. There is no explicit statement of when to prefer this over cm_results_read/cm_results_summary, and no prerequisites or exclusions.

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