Harness MCP Server

harness_describe

Read-only

Describe available resource types, their operations, and fields. Use this metadata to discover which resource types to query with other tools.

Instructions

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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "harness_describe"
  }
}

Input Schema

Name	Required	Description
`resource_type`	No	Get details for a specific resource type
`toolset`	No	Filter to a specific toolset
`search_term`	No	Search for resource types by keyword (matches type name, display name, toolset, description)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.8.3Jun 22, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds that no API call is made, confirming it's a safe, local operation. This provides behavioral clarity 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 two concise sentences: the first states core functionality, the second adds usage guidance. No extraneous information, efficiently front-loaded.

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

Completeness4/5

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

Given no output schema, the description explains the tool returns metadata about resource types, operations, and fields. This is sufficient for a discovery tool, though more detail on output format could be helpful.

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

Parameters3/5

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

Schema coverage is 100% with each parameter described (e.g., 'Get details for a specific resource type'). The description does not add further meaning beyond what the schema already provides, meeting the baseline.

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 describes available Harness resource types, their supported operations, and fields. It distinguishes itself as a local metadata-only tool to discover resource types for other harness_ tools, setting it apart from siblings like harness_create or harness_get.

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 explicitly says 'No API call — returns local metadata only' and advises using it to discover resource types for other tools. While it doesn't list when not to use, it provides clear context and purpose.

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

Deploy Server