Skip to main content
Glama
harness

Harness MCP Server

Official
by harness

harness_execute

Destructive

Execute actions on Harness resources—run/retry pipelines, toggle feature flags, test connectors, sync GitOps apps, run chaos experiments, or run HQL queries. Pass a URL to auto-extract IDs; enable wait to block until completion.

Instructions

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'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoHarness UI URL — auto-extracts org, project, type, and ID
bodyNoAdditional body payload for the action
waitNoFor pipeline run/retry actions: block until the execution reaches a terminal status (Success/Failed/Aborted/Errored/Expired). Server-side polling — a single tool call gives the agent the final outcome instead of an LLM polling loop. Ignored for other actions.
actionYesAction to execute (e.g. run, retry, interrupt, toggle, test_connection, sync)
inputsNoPipeline runtime inputs. For v0 pipeline, check runtime_input_template and pass key-value pairs or full overlay YAML. For pipeline_v1, check runtime_input_template_v1 and pass named values; the server sends them as an inputs: YAML document.
org_idNoOrganization identifier. Required for org- and project-scoped resources unless a Harness URL is passed. This session has no configured default (common in hosted/multi-user HTTP) — pass the current org_id on the first call. Do not omit it.
paramsNoAction-specific parameters. Call harness_describe for available fields per resource_type.
confirmNoSet to true to confirm the operation. Only required when the action's risk is medium_write or above (e.g. pipeline.run is high_write; hql_query.run/validate are read and need no confirmation) AND the client cannot surface a confirmation prompt — e.g. managed MCP that does not advertise elicitation, or an elicitation that fails at runtime. Has no effect for low-risk actions. Does NOT override an explicit decline from a client that completed an elicitation prompt — a user's decline is authoritative.
queriesNoBatch HQL queries — use with resource_type='hql_query' and action='validate' or 'run'. Fans out in parallel, returns per-query results.
project_idNoProject identifier. Required for project-scoped resources unless a Harness URL is passed. This session has no configured default (common in hosted/multi-user HTTP) — pass the current project_id on the first call. Do not omit it.
resource_idNoPrimary resource identifier
input_set_idsNoInput set IDs for complex pipelines. List available: harness_list(resource_type='input_set', filters={pipeline_id: '...'}).
resource_typeNoResource type with executable actions. Auto-detected from url.
resource_scopeNoScope for the operation. account: account-level resources only — do not use account to skip a known org/project. org: org-level (org_id). project: org+project. Omit to use the resource's default scope. Auto-detected from url when present.
wait_timeout_secondsNoMax seconds to wait when wait=true. Default 600 (10 min). Max 7200 (2 h). When the timeout fires, returns execution_timed_out=true with the last observed status.
wait_poll_interval_secondsNoInitial poll interval when wait=true (seconds). Default 3. Backoff multiplier 1.5x, capped at 30s.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.2.28
    • changedInput schema / properties / resource_type / enum
      Previous value: -[
      -  "alert",
      -  "approval_instance",
      -  "attestation",
      -  "chaos_action",
      -  "chaos_action_template",
      -  "chaos_experiment",
      -  "chaos_experiment_template",
      -  "chaos_fault",
      -  "chaos_fault_template",
      -  "chaos_guard_rule",
      -  "chaos_k8s_infrastructure",
      -  "chaos_loadtest",
      -  "chaos_probe",
      -  "chaos_probe_template",
      -  "chaos_risk_scan",
      -  "chaos_service",
      -  "commit",
      -  "connector",
      -  "cost_anomaly",
      -  "cost_budget",
      -  "cost_perspective",
      -  "cost_perspective_folder",
      -  "cost_recommendation",
      -  "database_execute_llm_authoring_pipeline",
      -  "delegate_token",
      -  "environment",
      -  "eval_annotation",
      -  "eval_dataset",
      -  "eval_dataset_item",
      -  "eval_git_registration",
      -  "eval_metric",
      -  "eval_metric_set",
      -  "eval_run",
      -  "eval_suite",
      -  "eval_target",
      -  "evaluation",
      -  "execution",
      -  "file_content",
      -  "file_store",
      -  "fme_feature_flag",
      -  "fme_feature_flag_definition",
      -  "fme_rule_based_segment_definition",
      -  "fme_segment_definition",
      -  "freeze_window",
      -  "gitops_application",
      -  "global_freeze",
      -  "hql_query",
      -  "idp_workflow",
      -  "incident",
      -  "infrastructure",
      -  "online_eval",
      -  "pipeline",
      -  "pipeline_dynamic_execution",
      -  "pipeline_v1",
      -  "pr_reviewer",
      -  "pull_request",
      -  "scanned_risk",
      -  "scs_sbom_drift",
      -  "security_exemption",
      -  "user",
      -  "vibe_app_lifecycle",
      -  "vibe_project"
      -]New value: +[
      +  "ai_budget_override_request",
      +  "alert",
      +  "approval_instance",
      +  "attestation",
      +  "chaos_action",
      +  "chaos_action_template",
      +  "chaos_experiment",
      +  "chaos_experiment_template",
      +  "chaos_fault",
      +  "chaos_fault_template",
      +  "chaos_guard_rule",
      +  "chaos_k8s_infrastructure",
      +  "chaos_loadtest",
      +  "chaos_probe",
      +  "chaos_probe_template",
      +  "chaos_risk_scan",
      +  "chaos_service",
      +  "commit",
      +  "connector",
      +  "cost_anomaly",
      +  "cost_budget",
      +  "cost_perspective",
      +  "cost_perspective_folder",
      +  "cost_recommendation",
      +  "database_execute_llm_authoring_pipeline",
      +  "delegate_token",
      +  "environment",
      +  "eval_annotation",
      +  "eval_dataset",
      +  "eval_dataset_item",
      +  "eval_git_registration",
      +  "eval_metric",
      +  "eval_metric_set",
      +  "eval_run",
      +  "eval_suite",
      +  "eval_target",
      +  "evaluation",
      +  "execution",
      +  "file_content",
      +  "file_store",
      +  "fme_feature_flag",
      +  "fme_feature_flag_definition",
      +  "fme_rule_based_segment_definition",
      +  "fme_segment_definition",
      +  "freeze_window",
      +  "gitops_application",
      +  "global_freeze",
      +  "hql_query",
      +  "idp_workflow",
      +  "incident",
      +  "infrastructure",
      +  "online_eval",
      +  "pipeline",
      +  "pipeline_dynamic_execution",
      +  "pipeline_v1",
      +  "pr_reviewer",
      +  "pull_request",
      +  "scanned_risk",
      +  "scs_sbom_drift",
      +  "security_exemption",
      +  "user",
      +  "vibe_app_lifecycle",
      +  "vibe_project"
      +]
  2. Changed1 schema field changedv3.2.26
    • changedInput schema / properties / resource_type / enum
      Previous value: -[
      -  "alert",
      -  "approval_instance",
      -  "attestation",
      -  "chaos_action",
      -  "chaos_action_template",
      -  "chaos_experiment",
      -  "chaos_experiment_template",
      -  "chaos_fault",
      -  "chaos_fault_template",
      -  "chaos_guard_rule",
      -  "chaos_k8s_infrastructure",
      -  "chaos_loadtest",
      -  "chaos_probe",
      -  "chaos_probe_template",
      -  "chaos_risk_scan",
      -  "chaos_service",
      -  "commit",
      -  "connector",
      -  "cost_anomaly",
      -  "cost_budget",
      -  "cost_perspective",
      -  "cost_perspective_folder",
      -  "cost_recommendation",
      -  "database_execute_llm_authoring_pipeline",
      -  "delegate_token",
      -  "environment",
      -  "eval_annotation",
      -  "eval_dataset",
      -  "eval_dataset_item",
      -  "eval_git_registration",
      -  "eval_metric",
      -  "eval_metric_set",
      -  "eval_run",
      -  "eval_suite",
      -  "eval_target",
      -  "evaluation",
      -  "execution",
      -  "file_content",
      -  "file_store",
      -  "fme_feature_flag",
      -  "fme_feature_flag_definition",
      -  "fme_rule_based_segment_definition",
      -  "freeze_window",
      -  "gitops_application",
      -  "global_freeze",
      -  "hql_query",
      -  "idp_workflow",
      -  "incident",
      -  "infrastructure",
      -  "online_eval",
      -  "pipeline",
      -  "pipeline_dynamic_execution",
      -  "pipeline_v1",
      -  "pr_reviewer",
      -  "pull_request",
      -  "scanned_risk",
      -  "scs_sbom_drift",
      -  "security_exemption",
      -  "user"
      -]New value: +[
      +  "alert",
      +  "approval_instance",
      +  "attestation",
      +  "chaos_action",
      +  "chaos_action_template",
      +  "chaos_experiment",
      +  "chaos_experiment_template",
      +  "chaos_fault",
      +  "chaos_fault_template",
      +  "chaos_guard_rule",
      +  "chaos_k8s_infrastructure",
      +  "chaos_loadtest",
      +  "chaos_probe",
      +  "chaos_probe_template",
      +  "chaos_risk_scan",
      +  "chaos_service",
      +  "commit",
      +  "connector",
      +  "cost_anomaly",
      +  "cost_budget",
      +  "cost_perspective",
      +  "cost_perspective_folder",
      +  "cost_recommendation",
      +  "database_execute_llm_authoring_pipeline",
      +  "delegate_token",
      +  "environment",
      +  "eval_annotation",
      +  "eval_dataset",
      +  "eval_dataset_item",
      +  "eval_git_registration",
      +  "eval_metric",
      +  "eval_metric_set",
      +  "eval_run",
      +  "eval_suite",
      +  "eval_target",
      +  "evaluation",
      +  "execution",
      +  "file_content",
      +  "file_store",
      +  "fme_feature_flag",
      +  "fme_feature_flag_definition",
      +  "fme_rule_based_segment_definition",
      +  "fme_segment_definition",
      +  "freeze_window",
      +  "gitops_application",
      +  "global_freeze",
      +  "hql_query",
      +  "idp_workflow",
      +  "incident",
      +  "infrastructure",
      +  "online_eval",
      +  "pipeline",
      +  "pipeline_dynamic_execution",
      +  "pipeline_v1",
      +  "pr_reviewer",
      +  "pull_request",
      +  "scanned_risk",
      +  "scs_sbom_drift",
      +  "security_exemption",
      +  "user",
      +  "vibe_app_lifecycle",
      +  "vibe_project"
      +]
  3. Changed1 schema field changedv3.2.25
    • changedInput schema / properties / inputs / description
      Previous value: -"Pipeline runtime inputs: key-value pairs like {branch: 'main'} (auto-resolved), or full YAML string. Check runtime_input_template first via harness_get."New value: +"Pipeline runtime inputs. For v0 pipeline, check runtime_input_template and pass key-value pairs or full overlay YAML. For pipeline_v1, check runtime_input_template_v1 and pass named values; the server sends them as an inputs: YAML document."
  4. Changed4 schema fields changedv3.2.22
    • changedInput schema / properties / org_id / description
      Previous value: -"Organization identifier (overrides default)"New value: +"Organization identifier. Required for org- and project-scoped resources unless a Harness URL is passed. This session has no configured default (common in hosted/multi-user HTTP) — pass the current org_id on the first call. Do not omit it."
    • changedInput schema / properties / project_id / description
      Previous value: -"Project identifier (overrides default)"New value: +"Project identifier. Required for project-scoped resources unless a Harness URL is passed. This session has no configured default (common in hosted/multi-user HTTP) — pass the current project_id on the first call. Do not omit it."
    • changedInput schema / properties / resource_scope / description
      Previous value: -"Scope for the operation. account: omit org/project (e.g. /v1/templates). org: org only. project: org+project. Auto-detected from url when present."New value: +"Scope for the operation. account: account-level resources only — do not use account to skip a known org/project. org: org-level (org_id). project: org+project. Omit to use the resource's default scope. Auto-detected from url when present."
    • changedInput schema / properties / resource_type / enum
      Previous value: -[
      -  "approval_instance",
      -  "attestation",
      -  "chaos_action",
      -  "chaos_action_template",
      -  "chaos_experiment",
      -  "chaos_experiment_template",
      -  "chaos_fault",
      -  "chaos_fault_template",
      -  "chaos_guard_rule",
      -  "chaos_k8s_infrastructure",
      -  "chaos_loadtest",
      -  "chaos_probe",
      -  "chaos_probe_template",
      -  "chaos_risk_scan",
      -  "chaos_service",
      -  "commit",
      -  "connector",
      -  "cost_anomaly",
      -  "cost_budget",
      -  "cost_perspective",
      -  "cost_perspective_folder",
      -  "cost_recommendation",
      -  "database_execute_llm_authoring_pipeline",
      -  "delegate_token",
      -  "environment",
      -  "eval_annotation",
      -  "eval_dataset",
      -  "eval_dataset_item",
      -  "eval_git_registration",
      -  "eval_metric",
      -  "eval_metric_set",
      -  "eval_run",
      -  "eval_suite",
      -  "eval_target",
      -  "evaluation",
      -  "execution",
      -  "file_content",
      -  "file_store",
      -  "fme_feature_flag",
      -  "fme_feature_flag_definition",
      -  "fme_rule_based_segment_definition",
      -  "freeze_window",
      -  "gitops_application",
      -  "global_freeze",
      -  "hql_query",
      -  "idp_workflow",
      -  "incident",
      -  "infrastructure",
      -  "online_eval",
      -  "pipeline",
      -  "pipeline_dynamic_execution",
      -  "pipeline_v1",
      -  "pr_reviewer",
      -  "pull_request",
      -  "scanned_risk",
      -  "scs_sbom_drift",
      -  "security_exemption",
      -  "user"
      -]New value: +[
      +  "alert",
      +  "approval_instance",
      +  "attestation",
      +  "chaos_action",
      +  "chaos_action_template",
      +  "chaos_experiment",
      +  "chaos_experiment_template",
      +  "chaos_fault",
      +  "chaos_fault_template",
      +  "chaos_guard_rule",
      +  "chaos_k8s_infrastructure",
      +  "chaos_loadtest",
      +  "chaos_probe",
      +  "chaos_probe_template",
      +  "chaos_risk_scan",
      +  "chaos_service",
      +  "commit",
      +  "connector",
      +  "cost_anomaly",
      +  "cost_budget",
      +  "cost_perspective",
      +  "cost_perspective_folder",
      +  "cost_recommendation",
      +  "database_execute_llm_authoring_pipeline",
      +  "delegate_token",
      +  "environment",
      +  "eval_annotation",
      +  "eval_dataset",
      +  "eval_dataset_item",
      +  "eval_git_registration",
      +  "eval_metric",
      +  "eval_metric_set",
      +  "eval_run",
      +  "eval_suite",
      +  "eval_target",
      +  "evaluation",
      +  "execution",
      +  "file_content",
      +  "file_store",
      +  "fme_feature_flag",
      +  "fme_feature_flag_definition",
      +  "fme_rule_based_segment_definition",
      +  "freeze_window",
      +  "gitops_application",
      +  "global_freeze",
      +  "hql_query",
      +  "idp_workflow",
      +  "incident",
      +  "infrastructure",
      +  "online_eval",
      +  "pipeline",
      +  "pipeline_dynamic_execution",
      +  "pipeline_v1",
      +  "pr_reviewer",
      +  "pull_request",
      +  "scanned_risk",
      +  "scs_sbom_drift",
      +  "security_exemption",
      +  "user"
      +]
  5. Changed1 schema field changedv3.2.21
    • changedInput schema / properties / resource_type / enum
      Previous value: -[
      -  "approval_instance",
      -  "attestation",
      -  "chaos_action",
      -  "chaos_action_template",
      -  "chaos_experiment",
      -  "chaos_experiment_template",
      -  "chaos_fault",
      -  "chaos_fault_template",
      -  "chaos_guard_rule",
      -  "chaos_k8s_infrastructure",
      -  "chaos_loadtest",
      -  "chaos_probe",
      -  "chaos_probe_template",
      -  "chaos_risk_scan",
      -  "chaos_service",
      -  "commit",
      -  "connector",
      -  "cost_anomaly",
      -  "cost_budget",
      -  "cost_perspective",
      -  "cost_perspective_folder",
      -  "cost_recommendation",
      -  "database_execute_llm_authoring_pipeline",
      -  "delegate_token",
      -  "environment",
      -  "eval_annotation",
      -  "eval_dataset",
      -  "eval_dataset_item",
      -  "eval_git_registration",
      -  "eval_metric",
      -  "eval_metric_set",
      -  "eval_run",
      -  "eval_suite",
      -  "eval_target",
      -  "evaluation",
      -  "execution",
      -  "file_content",
      -  "file_store",
      -  "fme_feature_flag",
      -  "fme_rule_based_segment_definition",
      -  "freeze_window",
      -  "gitops_application",
      -  "global_freeze",
      -  "hql_query",
      -  "idp_workflow",
      -  "incident",
      -  "infrastructure",
      -  "online_eval",
      -  "pipeline",
      -  "pipeline_dynamic_execution",
      -  "pipeline_v1",
      -  "pr_reviewer",
      -  "pull_request",
      -  "scanned_risk",
      -  "scs_sbom_drift",
      -  "security_exemption",
      -  "user"
      -]New value: +[
      +  "approval_instance",
      +  "attestation",
      +  "chaos_action",
      +  "chaos_action_template",
      +  "chaos_experiment",
      +  "chaos_experiment_template",
      +  "chaos_fault",
      +  "chaos_fault_template",
      +  "chaos_guard_rule",
      +  "chaos_k8s_infrastructure",
      +  "chaos_loadtest",
      +  "chaos_probe",
      +  "chaos_probe_template",
      +  "chaos_risk_scan",
      +  "chaos_service",
      +  "commit",
      +  "connector",
      +  "cost_anomaly",
      +  "cost_budget",
      +  "cost_perspective",
      +  "cost_perspective_folder",
      +  "cost_recommendation",
      +  "database_execute_llm_authoring_pipeline",
      +  "delegate_token",
      +  "environment",
      +  "eval_annotation",
      +  "eval_dataset",
      +  "eval_dataset_item",
      +  "eval_git_registration",
      +  "eval_metric",
      +  "eval_metric_set",
      +  "eval_run",
      +  "eval_suite",
      +  "eval_target",
      +  "evaluation",
      +  "execution",
      +  "file_content",
      +  "file_store",
      +  "fme_feature_flag",
      +  "fme_feature_flag_definition",
      +  "fme_rule_based_segment_definition",
      +  "freeze_window",
      +  "gitops_application",
      +  "global_freeze",
      +  "hql_query",
      +  "idp_workflow",
      +  "incident",
      +  "infrastructure",
      +  "online_eval",
      +  "pipeline",
      +  "pipeline_dynamic_execution",
      +  "pipeline_v1",
      +  "pr_reviewer",
      +  "pull_request",
      +  "scanned_risk",
      +  "scs_sbom_drift",
      +  "security_exemption",
      +  "user"
      +]
  6. Changed1 schema field changedv3.2.20
    • changedInput schema / properties / resource_type / enum
      Previous value: -[
      -  "approval_instance",
      -  "chaos_action",
      -  "chaos_action_template",
      -  "chaos_experiment",
      -  "chaos_experiment_template",
      -  "chaos_fault",
      -  "chaos_fault_template",
      -  "chaos_guard_rule",
      -  "chaos_k8s_infrastructure",
      -  "chaos_loadtest",
      -  "chaos_probe",
      -  "chaos_probe_template",
      -  "chaos_risk_scan",
      -  "commit",
      -  "connector",
      -  "cost_anomaly",
      -  "cost_perspective",
      -  "cost_perspective_folder",
      -  "cost_recommendation",
      -  "database_execute_llm_authoring_pipeline",
      -  "delegate_token",
      -  "environment",
      -  "eval_annotation",
      -  "eval_dataset",
      -  "eval_dataset_item",
      -  "eval_git_registration",
      -  "eval_metric",
      -  "eval_metric_set",
      -  "eval_run",
      -  "eval_suite",
      -  "eval_target",
      -  "evaluation",
      -  "execution",
      -  "file_content",
      -  "file_store",
      -  "fme_feature_flag",
      -  "fme_rule_based_segment_definition",
      -  "freeze_window",
      -  "gitops_application",
      -  "global_freeze",
      -  "hql_query",
      -  "idp_workflow",
      -  "incident",
      -  "infrastructure",
      -  "online_eval",
      -  "pipeline",
      -  "pipeline_dynamic_execution",
      -  "pipeline_v1",
      -  "pr_reviewer",
      -  "pull_request",
      -  "scanned_risk",
      -  "scs_sbom_drift",
      -  "security_exemption",
      -  "user"
      -]New value: +[
      +  "approval_instance",
      +  "attestation",
      +  "chaos_action",
      +  "chaos_action_template",
      +  "chaos_experiment",
      +  "chaos_experiment_template",
      +  "chaos_fault",
      +  "chaos_fault_template",
      +  "chaos_guard_rule",
      +  "chaos_k8s_infrastructure",
      +  "chaos_loadtest",
      +  "chaos_probe",
      +  "chaos_probe_template",
      +  "chaos_risk_scan",
      +  "chaos_service",
      +  "commit",
      +  "connector",
      +  "cost_anomaly",
      +  "cost_budget",
      +  "cost_perspective",
      +  "cost_perspective_folder",
      +  "cost_recommendation",
      +  "database_execute_llm_authoring_pipeline",
      +  "delegate_token",
      +  "environment",
      +  "eval_annotation",
      +  "eval_dataset",
      +  "eval_dataset_item",
      +  "eval_git_registration",
      +  "eval_metric",
      +  "eval_metric_set",
      +  "eval_run",
      +  "eval_suite",
      +  "eval_target",
      +  "evaluation",
      +  "execution",
      +  "file_content",
      +  "file_store",
      +  "fme_feature_flag",
      +  "fme_rule_based_segment_definition",
      +  "freeze_window",
      +  "gitops_application",
      +  "global_freeze",
      +  "hql_query",
      +  "idp_workflow",
      +  "incident",
      +  "infrastructure",
      +  "online_eval",
      +  "pipeline",
      +  "pipeline_dynamic_execution",
      +  "pipeline_v1",
      +  "pr_reviewer",
      +  "pull_request",
      +  "scanned_risk",
      +  "scs_sbom_drift",
      +  "security_exemption",
      +  "user"
      +]
  7. Changed1 schema field changedv3.2.17
    • changedInput schema / properties / resource_type / enum
      Previous value: -[
      -  "approval_instance",
      -  "chaos_action",
      -  "chaos_action_template",
      -  "chaos_experiment",
      -  "chaos_experiment_template",
      -  "chaos_fault",
      -  "chaos_fault_template",
      -  "chaos_guard_rule",
      -  "chaos_k8s_infrastructure",
      -  "chaos_loadtest",
      -  "chaos_probe",
      -  "chaos_probe_template",
      -  "commit",
      -  "connector",
      -  "cost_anomaly",
      -  "cost_perspective",
      -  "cost_perspective_folder",
      -  "cost_recommendation",
      -  "database_execute_llm_authoring_pipeline",
      -  "delegate_token",
      -  "environment",
      -  "eval_annotation",
      -  "eval_dataset",
      -  "eval_dataset_item",
      -  "eval_git_registration",
      -  "eval_metric",
      -  "eval_metric_set",
      -  "eval_run",
      -  "eval_suite",
      -  "eval_target",
      -  "evaluation",
      -  "execution",
      -  "file_content",
      -  "file_store",
      -  "fme_feature_flag",
      -  "fme_rule_based_segment_definition",
      -  "freeze_window",
      -  "gitops_application",
      -  "global_freeze",
      -  "hql_query",
      -  "idp_workflow",
      -  "incident",
      -  "infrastructure",
      -  "online_eval",
      -  "pipeline",
      -  "pipeline_dynamic_execution",
      -  "pipeline_v1",
      -  "pr_reviewer",
      -  "pull_request",
      -  "scs_sbom_drift",
      -  "security_exemption",
      -  "user"
      -]New value: +[
      +  "approval_instance",
      +  "chaos_action",
      +  "chaos_action_template",
      +  "chaos_experiment",
      +  "chaos_experiment_template",
      +  "chaos_fault",
      +  "chaos_fault_template",
      +  "chaos_guard_rule",
      +  "chaos_k8s_infrastructure",
      +  "chaos_loadtest",
      +  "chaos_probe",
      +  "chaos_probe_template",
      +  "chaos_risk_scan",
      +  "commit",
      +  "connector",
      +  "cost_anomaly",
      +  "cost_perspective",
      +  "cost_perspective_folder",
      +  "cost_recommendation",
      +  "database_execute_llm_authoring_pipeline",
      +  "delegate_token",
      +  "environment",
      +  "eval_annotation",
      +  "eval_dataset",
      +  "eval_dataset_item",
      +  "eval_git_registration",
      +  "eval_metric",
      +  "eval_metric_set",
      +  "eval_run",
      +  "eval_suite",
      +  "eval_target",
      +  "evaluation",
      +  "execution",
      +  "file_content",
      +  "file_store",
      +  "fme_feature_flag",
      +  "fme_rule_based_segment_definition",
      +  "freeze_window",
      +  "gitops_application",
      +  "global_freeze",
      +  "hql_query",
      +  "idp_workflow",
      +  "incident",
      +  "infrastructure",
      +  "online_eval",
      +  "pipeline",
      +  "pipeline_dynamic_execution",
      +  "pipeline_v1",
      +  "pr_reviewer",
      +  "pull_request",
      +  "scanned_risk",
      +  "scs_sbom_drift",
      +  "security_exemption",
      +  "user"
      +]
  8. First observedv3.2.10

TDQS

A4.8/5.0
Behavior5/5

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

Annotations (destructiveHint=true, readOnlyHint=false) indicate mutation, but the description adds substantial behavior: the wait option blocks until terminal status, the confirmation requirement for medium_write+ actions with client elicitation caveats, the URL auto-extraction, HQL batch fan-out, and timeout behavior returning execution_timed_out=true. It also explains that a user's explicit decline is authoritative. This goes far beyond the annotations.

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?

The description is about four sentences, each packed with value: example actions, URL auto-extraction, wait behavior, and HQL batch. The most critical usage guidance (wait, URL) is front-loaded. No filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 16 params, a large resource_type enum, nested objects, and an output schema, the description covers the key operational patterns: wait polling, confirmation for risky actions, URL-based identifier resolution, HQL batch, and pointer to harness_describe for param details. The output schema handles return values, so nothing critical is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds meaning beyond the schema: it explains that URL auto-extracts org/project/type/ID, that wait is server-side polling (single call vs LLM loop), the risk-based confirmation logic, and the HQL batch usage with resource_type='hql_query'. It also points to harness_describe for action-specific params, enriching the schema's flat descriptions.

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?

The description clearly states the tool executes actions on Harness resources, listing concrete examples like run/retry/interrupt pipelines, kill/restore FME feature flags, test connectors, and run chaos experiments. It distinguishes itself from read/list tools by emphasizing the action-execution role and mentions URL auto-extraction, making its purpose specific and differentiated.

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

Usage Guidelines4/5

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

It provides clear context for when to use this tool (executing actions) and gives usage specifics like passing a URL to auto-extract identifiers, using wait for terminal status, and the HQL batch pattern. It doesn't explicitly say 'use harness_describe for reads' but the sibling names and the description's action focus make the boundary implicit. A brief exclusion note would earn a 5.

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