Skip to main content
Glama

Pipeline (job hunt)

hunt_pipeline
Read-onlyIdempotent

The board: counts by stage first, then every non-terminal item with stage, last touch, open next action. On a long board, filter by status.

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": "hunt_pipeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNoFilter to one stage; "skipped" shows the skip list (pattern memory, JH-8).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already establish a safe, idempotent read, so the description's job is to add return-shape detail — and it does: counts first, then non-terminal items only, each with stage, last touch, and open next action. It also implicitly discloses that terminal items are excluded, which an agent cannot learn from the schema; it omits any pagination or size-limit behavior beyond the "long board" hint.

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?

Two compact sentences with the output order front-loaded and no filler. The telegraphic "The board:" construction is slightly clipped but never wastes a sentence.

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?

With no output schema declared, the description carries the return shape and does so accurately, and the sole parameter is fully covered by the schema. Nothing essential for correct invocation is missing, though sibling routing stays unaddressed.

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% and the single status param already documents filtering and the "skipped" skip-list behavior, so the baseline is 3. The description only adds a usage nudge (long board) rather than new syntax or allowed values.

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 board: counts by stage first, then every non-terminal item with stage, last touch, open next action" states the resource and exactly what comes back, which is more than the title provides. It never distinguishes this from crm_pipeline or hunt_due/hunt_contacts, so the agent must infer the boundary from the name alone.

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?

The only guidance is "On a long board, filter by status," which covers one parameter condition but never says when to reach for this tool versus hunt_due, hunt_contacts, or crm_pipeline. No exclusions or prerequisites are given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.