Skip to main content
Glama
Sign In
JobHound

JobHound

by Null-Phnix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

jobhound_pause

Pause the background daemon to stop automated job applications. Halt the scan loop for manual control.

Instructions

Pause the JobHound daemon (scan loop stops applying).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It explicitly states that the scan loop stops applying, which is the key behavioral effect. It does not cover edge cases like idempotency or in-flight operations, but the core behavior is clearly disclosed.

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 a single concise sentence that front-loads the action and resource, adding only the necessary clarification about the scan loop. Every word earns its place.

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?

For a zero-parameter tool with a clear output schema, the description adequately covers the tool's purpose and effect. Sibling names like jobhound_resume provide related context, making the description complete for an agent to select and invoke correctly.

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

Parameters4/5

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

The tool has zero parameters, so the description fully covers the semantics by simply stating the action. The baseline of 4 for no-parameter tools applies, and the description adds no confusion.

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 uses a specific verb 'Pause' and identifies the resource 'JobHound daemon', with clarifying detail 'scan loop stops applying' that clearly distinguishes it from sibling tools like jobhound_status or jobhound_resume.

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 implies usage context (when you want to halt scanning) but does not explicitly state when not to use or reference alternatives. However, the sibling tool jobhound_resume is implicitly complementary, making the usage clear enough.

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

Deploy Server

Other Tools