Skip to main content
Glama
Sign In
homestead-mcp

homestead-mcp

by Cmarl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

homestead_job

Poll progress of install or index build jobs by job ID until done or error.

Instructions

Progress of a homestead_install or homestead_index_build job. Poll until status is 'done' or 'error'.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "job_id": "<job_id>"
    },
    "name": "homestead_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It discloses that the tool is a polling operation and that statuses eventually reach 'done' or 'error', which is useful. However, it doesn't state whether the operation is read-only, what intermediate statuses may appear, or how errors are surfaced.

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 short sentences with no wasted words. The purpose is front-loaded and the polling condition is stated directly. Every phrase earns its place.

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?

For a simple one-parameter polling tool, the description is adequate: it names the job types, the polling behavior, and the terminal statuses. But without an output schema, it leaves the response shape and the source of job_id unstated, which are meaningful gaps for an AI agent.

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

Parameters2/5

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

Schema coverage is 0% and the description adds little about job_id beyond what the schema already shows. It implies the ID identifies a homestead_install or homestead_index_build job, but it never says where the job_id comes from or what format it takes, so the agent must guess or infer the source.

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 states the tool reports progress of a homestead_install or homestead_index_build job, and adds the polling behavior with terminal statuses 'done' or 'error'. This clearly distinguishes it from sibling tools like homestead_install and homestead_index_build, which start the jobs.

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?

It gives clear context: this is the follow-up polling tool for jobs launched by homestead_install or homestead_index_build, and instructs the agent to poll until a terminal status appears. It doesn't explicitly list when not to use it or name alternatives, but the intended usage is easy to infer.

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