Skip to main content
Glama
harness

Harness MCP Server

Official
by harness

harness_schema

Read-only

Fetch Harness YAML schema definitions or example snippets for any resource type. Drill into sections, search examples by keyword, or retrieve a full schema summary.

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.
identifierNoOptional entity identifier for NG yaml-schema. Use when updating an existing entity to fetch an entity-specific schema. Omit for generic create-time schemas — a placeholder identifier is sent automatically for all live entity types at any scope.
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 declare readOnlyHint=true and destructiveHint=false, and the description confirms no modifications occur. It adds value by detailing how schemas are sourced (bundled vs. live) and the identifier placeholder logic, providing transparency beyond annotations without contradiction.

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 well-structured: starts with core purpose, then parameter-by-parameter guidance with clear action verbs. It uses short sentences and bullet-style listing for resource types. Every sentence earns its place, avoiding redundancy while being thorough.

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 8 parameters, 0 required, and an output schema, the description covers all aspects: parameter combinations, live vs. bundled behavior, precedence, and example search filtering. It feels complete and leaves no ambiguity about how to use the tool.

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?

With 100% schema coverage, the description still adds meaning by explaining each parameter's role (e.g., path for drill-down, example for named examples, identifier for entity-specific schemas). It clarifies the fallback placeholder for identifier, which is not in the schema, and explains scope requirements.

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 fetches Harness YAML schemas or examples for a resource type, distinguishing between bundled and live schemas. It specifies the resource types and usage modes, making the purpose unmistakable and distinct from sibling CRUD tools.

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

Usage Guidelines5/5

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

The description provides explicit usage instructions: 'Use without path for a summary...', 'Use with path to drill...', 'Use with example...', and 'Use with example_search...'. It also gives precedence rules ('Precedence: example > example_search > path > summary') and clarifies when scope/org_id/project_id are needed.

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