Harness

Execute multiple HQL queries in a single call. Returns results (columns, rows, stats) for each query. Use this for KG analysis workflows that need data from several queries — much faster than sequential harness_execute(action='run') calls.

harness_batch_execute_hql

Validate multiple HQL queries in a single call. Returns validation results for each query. Use this instead of calling harness_execute(action='validate') multiple times — much faster for dashboards with many widgets.

harness_batch_validate_hql

Create a Harness resource. For pipelines/input sets: pass body as a YAML string directly (recommended for complex definitions), or use body.yamlPipeline (YAML string), or body.pipeline (JSON object). For remote pipelines, pass git details in params: external Git (store_type='REMOTE', connector_ref, repo_name, branch, file_path) or Harness Code (store_type='REMOTE', is_harness_code_repo=true, repo_name, branch, file_path). For others: call harness_describe for the body format.

harness_create

Delete a Harness resource. You can pass a Harness URL to auto-extract identifiers. This is destructive and cannot be undone.

harness_delete

Describe available Harness resource types, their supported operations, and fields. No API call — returns local metadata only. Use this to discover what resource_types you can use with other harness_ tools.

harness_describe

Diagnose a Harness resource — analyze failures, test connectivity, check health, or troubleshoot GitOps sync issues. Defaults to pipeline execution diagnosis. Accepts a Harness URL to auto-detect the resource type. When a TYPESAFE_API_KEY is configured, pipeline failures additionally include an advisory "triage" field classifying each failed step (category: infra_flake, test_failure, config_error, dependency_failure, permission_error, timeout; plus confidence) — failure messages, delegate info, and fetched log snippets are sent to the configured TypeSafe API to produce it; the field is omitted when the key is absent, triage is disabled, or classification times out or is low-confidence.

harness_diagnose

Execute an action on a Harness resource: run/retry/interrupt pipelines, kill/restore FME feature flags, test connectors, sync GitOps apps, run chaos experiments. You can pass a Harness URL to auto-extract identifiers. Pass `wait: true` for pipeline run/retry to block until the execution reaches a terminal status — single tool call instead of an LLM polling loop. For HQL batch operations pass `queries` with resource_type='hql_query' and action='validate' or 'run'.

harness_execute

Fetch a single HyperDash (HD) dashboard JSON-Schema root VERBATIM — full self-contained document (internal $defs + $schema preserved), suitable for strict JSON-Schema validation. Unlike harness_schema, this does NOT summarize or depth-limit the schema. ALWAYS GZIP: the response is ONLY ever the compressed schema in the `schema_gzip_b64` field (gzip then base64) — there is no uncompressed mode and no flag to request raw JSON. Every caller MUST decode it: base64-decode -> gunzip -> JSON.parse. Use to validate an emit_capability dashboard/widget payload against its canonical schema. Available roots: CapabilityMetadata, CartesianWidget, CreateDashboardPayload, DashboardContainer, DashboardFilterConfig, DashboardSchema, DonutWidget, GaugeWidget, GridContainerLayout, GridItemLayout, MetricWidget, PanelContainer, TableWidget, TabsWidgetContainer, TextWidget, UqlDataSource, WidgetPayload.

harness_hd_schema

Get a Harness resource by ID. Accepts a Harness URL to auto-extract identifiers. For failure analysis, prefer harness_diagnose.

harness_get

Fetch Harness YAML schema or examples for a resource type. Pipeline/template schemas are bundled from harness-schema; connector, environment, service, secret, and infrastructure schemas are fetched live from NG /yaml-schema (pass scope, org_id, project_id). release_process and release_activity schemas are fetched live from /gateway/rmg/api/yamlSchema. Use without path for a summary of fields and available sections. Use with path to drill into a specific section. Use with example to fetch a named example YAML snippet. Use with example_search to find examples by keyword. Precedence: example > example_search > path > summary. Available schemas: pipeline, template, trigger, pipeline_v1, template_v1, inputSet_v1, overlayInputSet_v1, agent-pipeline, hd_DashboardSchema, hd_DashboardContainer, hd_PanelContainer, hd_TabsWidgetContainer, hd_CartesianWidget, hd_DonutWidget, hd_GaugeWidget, hd_MetricWidget, hd_TableWidget, hd_TextWidget, hd_GridContainerLayout, hd_GridItemLayout, hd_UqlDataSource, hd_DashboardFilterConfig, hd_CreateDashboardPayload, hd_WidgetPayload, hd_CapabilityMetadata, dashboard_hd, connector, environment, service, secret, infrastructure, release_process, release_activity.

harness_schema