Skip to main content
Glama
Sign In
carmaker-mcp

carmaker-mcp

by dimitr-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Change log

cm_changelog
Read-only

Retrieve recorded CarMaker changes, including file keys, workspace variables, model parameters, and GUI settings with old and new values, filtered by session and entry limit.

Instructions

Recorded changes (file keys, workspace variables, model parameters, GUI settings) with old and new values.

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

Input Schema

NameRequiredDescriptionDefault
limitNoNewest entries to return
sessionNoSession id (default: this session; 'all' for every session)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.0
    • changedInput schema / properties / session / description
      Previous value: -"Session id (default: this session)"New value: +"Session id (default: this session; 'all' for every session)"
  2. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/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 useful context about what is recorded and that each entry carries both old and new values, but says nothing about ordering, pagination, or the cross-session scope controlled by the session parameter.

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 compact clause with no padding, and the most informative part - the list of change categories - is front-loaded. It is a noun phrase rather than a sentence, which costs it a step toward maximum clarity.

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?

An output schema exists so return values need no explanation, and annotations cover the read-only profile. However, for a log-retrieval tool with session scoping and limits, the description does not tell the agent what defaults apply or how entries are ordered, leaving gaps a caller would want filled.

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%, with limit and session both documented including the 'all' sentinel, so the schema does the heavy lifting. The description contributes nothing about parameters beyond the generic notion of entries, making the baseline 3 the right call.

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 a specific resource - recorded changes - and enumerates the kinds of changes captured (file keys, workspace variables, model parameters, GUI settings) plus the old/new value pairing. It never uses a verb, so the agent must infer that this retrieves the log, and it does not distinguish itself from nearby siblings such as cm_log or cm_diff.

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

Usage Guidelines2/5

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

There is no statement of when to call this tool, no prerequisites, and no mention of alternatives like cm_diff for comparing states or cm_log for the message stream. The agent must guess from the name alone that this is the audit-trail tool.

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