Camel

Showing 25 of 50 from the live probe.

• Camel Ai Pipeline Scaffold

  Generate a YAML DSL Camel route for an AI document-processing pipeline. Combines document processors (Docling for open-source/on-prem, Textract for AWS-managed) with Bedrock LLM services for summarization, extraction, RAG, or classification. Returns a runnable route and matching application.properties template.

• Camel Catalog Component Doc

  Get documentation for a Camel component: URI syntax and endpoint options. Default returns common options only (excludes deprecated and advanced). Set includeHeaders=true to also return message header metadata (CamelXxx names, constants, types). Use camel_catalog_component_maven for groupId/artifactId/version.

• Camel Catalog Component Maven

  Get Maven coordinates (groupId, artifactId, version) for a Camel component, for adding it as a dependency.

• Camel Catalog Components

  List available Camel components from the catalog. Returns component name, title, and labels (no description; call camel_catalog_component_doc for that). Use filter to search by name, label to filter by category.

• Camel Catalog Dataformat Doc

  Get detailed documentation for a Camel data format including all options, Maven coordinates, and configuration parameters.

• Camel Catalog Dataformats

  List available Camel data formats for marshalling/unmarshalling (e.g., json, xml, csv, avro, protobuf).

• Camel Catalog Doc

  Get the full AsciiDoc documentation page from the catalog. Returns the complete human-readable documentation with usage examples, code snippets, configuration guides, and best practices. This complements the structured tools (camel_catalog_component_doc, camel_catalog_eip_doc, etc.) which return parsed JSON with options and metadata. Use camel_catalog_docs to discover available page names. Naming conventions: components use '<name>-component' (e.g., 'kafka-component'), data formats use '<name>-d

• Camel Catalog Docs

  List available AsciiDoc documentation page names from the catalog. Returns page names (without .adoc extension) that can be passed to camel_catalog_doc to retrieve the full documentation content. Unlike the structured tools (camel_catalog_component_doc, camel_catalog_eip_doc, etc.) which return parsed JSON with options and metadata, the AsciiDoc pages contain the full human-readable documentation with usage examples, code snippets, and best practices. Only available from Camel 4.22 onwards.

• Camel Catalog Eip Doc

  Get detailed documentation for a Camel EIP (Enterprise Integration Pattern).

• Camel Catalog Eips

  List Camel Enterprise Integration Patterns (EIPs) like split, aggregate, filter, choice, multicast, circuit-breaker, etc. EIPs have aliases for common AI/modern terms (e.g., fan-out, scatter-gather, retry, dedup). Filter also matches aliases with dash normalization (fan-out, fanout, fanOut all match).

• Camel Catalog Example File

  Get the content of a specific file from a Camel CLI example. Use camel_catalog_examples first to find the example name and its files. Only bundled examples can return file contents directly; for non-bundled examples, a GitHub URL is returned instead.

• Camel Catalog Examples

  List available Camel CLI examples. Returns name, title, description, difficulty level, and tags. Use filter to search by name, description, or tag. Use level to filter by difficulty (beginner, intermediate, advanced).

• Camel Catalog Kamelet Doc

  Get detailed documentation for a specific Camel Kamelet including all properties/options, dependencies, and usage information.

• Camel Catalog Kamelets

  List available Camel Kamelets from the Kamelet Catalog. Returns kamelet name, type (source, sink, action), support level, and description. Use filter to search by name or description, type to filter by category.

• Camel Catalog Language Doc

  Get detailed documentation for a Camel expression language including all options, Maven coordinates, and configuration parameters.

• Camel Catalog Languages

  List available Camel expression languages (e.g., simple, jsonpath, xpath, groovy, jq).

• Camel Component Properties

  List valid configuration property keys for a Camel component, in the form camel.component.<scheme>.<name>. For each property the tool returns the option name, type, default value, required flag, deprecated flag, secret flag, enum choices and description. Endpoint options are also returned, since they can be set as component-level defaults via the same prefix in application.properties.

• Camel Configuration Validate

  Validate one or more Camel configuration property lines (e.g. lines from application.properties). Detects misspelled option names, invalid values (boolean/integer/number/duration/enum) and returns suggestions when available. The input can be a single line or a multi-line string with one property per line; blank lines and comments (starting with # or !) are skipped.

• Camel Dependency Check

  Check Camel project dependency hygiene. Given a pom.xml (and optionally route definitions), detects outdated Camel dependencies compared to the latest catalog version, missing Maven dependencies for components used in routes, and version conflicts between the Camel BOM and explicit dependency overrides. Returns actionable recommendations with corrected dependency snippets. POM content is automatically sanitized to mask sensitive data (passwords, tokens, API keys) unless sanitizePom is set to fal

• Camel Dependency Security Audit

  Perform a security vulnerability audit on a Camel project's dependencies. Cross-references the project's pom.xml dependencies with the Camel security advisory database to identify CVEs affecting each artifact at the project's Camel version. Reports severity, affected version ranges, fixed versions, and whether the vulnerable component is directly used (reachable) or only a transitive dependency. POM content is automatically sanitized to mask sensitive data.

• Camel Error Diagnose

  Diagnose a Camel error from a stack trace or error message. Returns the identified component/EIP involved, common causes for the error, links to relevant Camel documentation, and suggested fixes. Covers the most common Camel exceptions including NoSuchEndpointException, ResolveEndpointFailedException, FailedToCreateRouteException, and more.

• Camel Migration Analyze

  Analyze a Camel project's pom.xml to detect the runtime type (main, spring-boot, quarkus, wildfly, karaf), Camel version, Java version, and Camel component dependencies. This is the first step in a migration workflow. POM content is automatically sanitized to mask sensitive data (passwords, tokens, API keys) unless sanitizePom is set to false.

• Camel Migration Compatibility

  Check migration compatibility for Camel components by providing relevant migration guide URLs and Java version requirements. The LLM should consult the migration guides for detailed component rename mappings and API changes.

• Camel Migration Guide Search

  Search Camel migration and upgrade guides for a specific term or component name. Returns matching snippets from the official guides with version info and URLs. Supports fuzzy matching for typo tolerance. Use this instead of web search when looking up migration-related changes, removed components, API renames, or breaking changes.

• Camel Migration Recipes

  Get Maven commands to run Camel OpenRewrite migration recipes for upgrading between versions. Returns the exact Maven commands to execute on the project. PREREQUISITE: The project MUST compile successfully ('mvn clean compile' must pass) BEFORE running the OpenRewrite recipes. If the project does not compile, fix the build errors first. OpenRewrite requires a compilable project to parse and transform the code.