Skip to main content
Glama

list_harnesses

Read-only

List natural-language harness specs to control workflows, verify proofs, and execute GTM strategies. Filter by tag for specific needs.

Instructions

List natural-language harness specs for portable workflow control, proof-backed verification, and GTM execution.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoOptional tag filter such as verification, acquisition, or workflow.

Implementation Reference

  • Handler function for list_harnesses. Loads harness files from the HARNESS_DIR directory, optionally filtered by tag, and returns a simplified catalog with id, title, description, tags, inputs, and sourcePath.
    function listHarnesses(options = {}) {
      return loadHarnesses(options).map((harness) => ({
        id: harness.id,
        title: harness.title,
        description: harness.description,
        tags: harness.tags,
        inputs: Object.keys(harness.inputSchema),
        sourcePath: harness.sourcePath,
      }));
    }
  • Helper function that reads .md harness files from the HARNESS_DIR directory, parses them, and optionally filters by tag.
    function loadHarnesses(options = {}) {
      if (!fs.existsSync(HARNESS_DIR)) {
        return [];
      }
    
      const harnesses = fs.readdirSync(HARNESS_DIR)
        .filter((entry) => entry.endsWith('.md'))
        .sort()
        .map((entry) => loadHarnessFile(path.join(HARNESS_DIR, entry)));
    
      if (options.tag) {
        return harnesses.filter((harness) => harness.tags.includes(String(options.tag)));
      }
    
      return harnesses;
    }
  • Tool registration in the TOOLS array with name 'list_harnesses', description, and input schema defining an optional 'tag' filter parameter.
    readOnlyTool({
      name: 'list_harnesses',
      description: 'List natural-language harness specs for portable workflow control, proof-backed verification, and GTM execution.',
      inputSchema: {
        type: 'object',
        properties: {
          tag: { type: 'string', description: 'Optional tag filter such as verification, acquisition, or workflow.' },
        },
      },
    }),
  • MCP server switch-case dispatching the 'list_harnesses' tool call. Imports listHarnesses from natural-language-harness.js and returns the result as text.
    case 'list_harnesses':
      return toTextResult({ harnesses: listHarnesses({ tag: args.tag }) });
Behavior3/5

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

Annotations already indicate readOnlyHint, so description is consistent. However, no additional behavioral details like pagination or output format are provided.

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?

Single sentence, concise, front-loads the verb. No wasted words.

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

Completeness3/5

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

Simple tool but no output schema and description does not hint at return format. Adequate for a basic list operation, but could be more complete.

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 a clear parameter description for 'tag'. The tool description adds no extra value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists 'natural-language harness specs' for specific purposes. However, it does not explicitly distinguish from sibling 'run_harness' tool, and the jargon may be unclear.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like 'run_harness' or when a tag filter is appropriate. Context and exclusions are missing.

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/IgorGanapolsky/ThumbGate'

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