Skip to main content
Glama
Sign In
antiSMASH MCP Server

antiSMASH MCP Server

by ZengZichao
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

wait_for_job

Poll an antiSMASH job status at intervals until it completes or errors, with configurable maximum wait and poll interval for long-running analyses.

Instructions

Wait for an antiSMASH job to complete by polling its status. This is a blocking operation that checks the job status at regular intervals until the job is done or an error occurs. Use with caution as antiSMASH analysis can take 10+ minutes.

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

Input Schema

NameRequiredDescriptionDefault
job_idYesThe antiSMASH job ID to wait for.
max_waitNoMaximum seconds to wait before giving up.
server_typeNoType of antiSMASH server the job was submitted to.bacteria
poll_intervalNoSeconds between status checks.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that the call is blocking, polls at regular intervals, terminates on completion or error, and can run 10+ minutes. It omits what happens on hitting max_wait (timeout behavior) and permissions, which keeps it short of a 5.

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?

Three sentences, each earning its place: purpose first, blocking/mechanism second, cost warning third. No filler or repetition of schema details.

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?

There is no output schema, so the description should say what the tool returns on success (final job status only, or results), and it does not. The behavioral narrative is adequate for a single blocking call, but the return contract is left undefined.

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 schema already documents job_id, max_wait, server_type, and poll_interval with defaults and an enum. The description only adds the vague notion of 'regular intervals' for polling, which the schema covers better, so the baseline 3 applies.

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 verb and resource ('Wait for an antiSMASH job to complete by polling its status'), which is clear and actionable. However, it does not distinguish itself from the sibling check_job_status, which by name performs an analogous status check, so the agent must infer the blocking vs. non-blocking difference.

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

Usage Guidelines3/5

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

'Use with caution as antiSMASH analysis can take 10+ minutes' gives implicit guidance about when the blocking cost is justified, but no alternative (e.g., check_job_status for non-blocking polling) is named. Usage is implied rather than explicitly routed.

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