Skip to main content
Glama

generate_config_from_build_log

Parses an IDE build log to generate a Delphi configuration file, with minimal settings for Windows targets and full library paths for cross-compilation targets.

Instructions

Generate delphi_config.toml file automatically by parsing an IDE build log. For Windows targets, generates a minimal config with only the Delphi installation path (MSBuild handles all other settings). For cross-compilation targets (Linux64/Android), generates a full config with all library paths and compiler settings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
build_log_pathYesAbsolute path to IDE build log file
output_config_pathNoOutput path for generated config file. If not specified, generates platform-specific filename (e.g., delphi_config_win32.toml) by default.
use_platform_specific_nameNoGenerate platform-specific filename (e.g., delphi_config_win64.toml) based on detected platform. Set to false for generic delphi_config.toml. Ignored if output_config_path is specified.
use_env_varsNoReplace user paths with ${USERNAME} environment variable
Behavior3/5

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

Provides target-specific behavior details (minimal vs full config) beyond annotations, but omits important aspects like file overwrite behavior, error handling, and permissions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two efficient sentences, front-loaded with purpose followed by platform differentiation; no wasted words.

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?

Covers main functionality and platform differences, but lacks details on output format, success/failure behavior, and usage context relative to sibling 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?

Input schema covers all parameters (100% coverage), and the description adds no additional parameter explanation, meeting baseline but not exceeding.

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?

Clearly states the tool generates a config file from an IDE build log, and distinguishes behavior for Windows vs cross-compilation targets.

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?

Implies usage for single build log config generation, but lacks explicit guidance on when not to use or comparison with sibling tools like extend_config_from_build_log.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Basti-Fantasti/delphi-build-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server