AlpineLead OI

Run autonomous hunter now

hunter_run

Use after Hunter is configured when the user wants a fresh autonomous prospecting run now. Returns only accepted opportunities plus usage information.

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

Input Schema

Name	Required	Description	Default
`force`	No	Run immediately even if the Hunter's scheduled time is not yet due.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 23, 2026

TDQS

A4/5.0

Behavior4/5

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

Given annotations already mark this as non-read-only and non-destructive, the description adds useful behavioral detail: this is a fresh run and only accepted opportunities plus usage information are returned. It does not mention cost side effects or external actions, but with annotations carrying the safety profile plus an output schema, this is adequate.

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?

Two tight sentences with no waste. The precondition, trigger, and return scope are all front-loaded, making the description immediately actionable.

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?

For a tool with one optional parameter and an output schema, the description covers the essentials: prerequisite, invocation timing, and result filtering. It could briefly mention cost or external side effects, but it is not incomplete enough to confuse an agent.

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 description coverage is 100%, so the Boolean force parameter is already documented. The description does not add parameter-specific meaning, so it correctly relies on the schema for this dimension.

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 states a specific action: run an autonomous prospecting run 'now' after Hunter is configured, and clarifies the return scope ('only accepted opportunities plus usage information'). It distinguishes itself from siblings by emphasizing a fresh immediate run, though it does not explicitly name a contrasting sibling.

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?

'Use after Hunter is configured' is an explicit precondition, and 'when the user wants a fresh autonomous prospecting run now' clearly identifies the triggering situation. It provides clear context but does not explicitly list when not to use it or name alternative tools.

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

All AlpineLead OI tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?