Skip to main content
Glama
harness

Harness MCP Server

Official
by harness

harness_schema

Read-only

Retrieve YAML schema definitions and examples for Harness resource types such as pipelines, templates, connectors, and infrastructure.

Instructions

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). 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, connector, environment, service, secret, infrastructure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoDot-separated path to drill into a specific definition section. Omit for a top-level summary showing all available sections.
scopeNoHarness YAML scope for live entity schemas (connector, environment, service, secret, infrastructure). Defaults to account. Org/project scoped entities require org_id and/or project_id.
org_idNoOrganization identifier — required when scope is org or project (live entity schemas).
exampleNoFetch a specific example by name (e.g. 'minimal-ci'). Returns the full YAML snippet and description.
project_idNoProject identifier — required when scope is project (live entity schemas).
resource_typeNoSchema to fetch. Available: pipeline, template, trigger, pipeline_v1, template_v1, inputSet_v1, overlayInputSet_v1, agent-pipeline, connector, environment, service, secret, infrastructure. Required for schema/path lookups, optional for example_search.
example_searchNoSearch examples by keyword. Returns matching example names and descriptions. Optionally combine with resource_type to filter.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds valuable behavioral context: explains that schemas are either bundled (pipeline/template) or fetched live (connector et al.), and that scope/org/project are needed for live entities. It also reveals the precedence behavior, which is not in annotations.

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?

The description is two well-structured sentences. It starts with purpose, then lists modes, precedence, and available schemas. It is dense but not verbose. Slightly more conciseness could be achieved by reducing redundancy (e.g., 'Available schemas' list is duplicated from parameter enum), but overall efficient.

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?

The description covers all modes (summary, path drill, example, example_search), explains the two schema sources (bundled vs live), lists all 13 resource types, states precedence, and clarifies scope requirements. An output schema exists, so return values need not be described. For a tool with 7 parameters and live data dependencies, this is comprehensive.

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

Parameters4/5

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

Schema description coverage is 100% (all 7 parameters documented). The description adds value beyond the schema: it groups parameters by usage mode, explains precedence (example > example_search > path > summary), and notes defaults (scope defaults to account). This enhances understanding of how parameters interact.

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 verb 'Fetch' and resource 'Harness YAML schema or examples'. It distinguishes itself from siblings (CRUD tools) as a read-only schema retrieval tool. The multiple modes are explicitly listed, providing a complete picture of what the tool does.

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?

The description provides explicit guidance for different parameter combinations: 'Use without path for a summary... Use with path to drill... Use with example... Use with example_search...' It also states the precedence. However, it does not explicitly compare to sibling tools or state when not to use, but the context is sufficient.

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/harness/mcp-server'

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