Skip to main content
Glama
yyy188
by yyy188

get_bootstrap_progress

Check the progress of a bootstrap model job, returning its status, phase-based progress, and completion state.

Instructions

Poll the progress of a bootstrap_models job.

After calling bootstrap_models, poll this roughly every 2 minutes, reporting
each sample (status, progress %, message) to the user, until status is DONE
or ERROR. Progress is phase-based, not live bytes: the embedding
(~130MB ONNX, via fastembed) lacks per-chunk byte callbacks, so `message`
reports phase transitions rather than byte counts. When the reranker is
enabled (RERANKER_ENABLED=1) a second phase downloads the ~80MB reranker;
otherwise bootstrap completes after the embedding model alone.

Returns:
    {"job_id","project_id","kind","status","progress","total","done",
     "message","started_at","finished_at"} (project_id is 0 for a
    bootstrap job — it has no project). status is one of
    PENDING | RUNNING | DONE | ERROR.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
job_idYes
Behavior5/5

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

No annotations provided, so description carries full burden. It fully discloses that progress is phase-based not live bytes, explains the embedding and reranker phases with sizes, and lists return fields and status values.

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?

The description is well-structured with a clear first line stating purpose, then usage, then technical details. It is somewhat lengthy but each sentence adds value. Could be slightly more concise.

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 polling tool with phases and no output schema, the description is very complete. It explains behavior, return fields, status enum, and edge case (project_id=0 for bootstrap jobs). No missing information.

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?

The single parameter job_id is not described in the description (schema coverage 0%). The name is self-explanatory but the description could have clarified where to obtain it (e.g., from bootstrap_models response). Minimal added value beyond schema.

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 clearly states the verb 'Poll' and the resource 'progress of a bootstrap_models job'. It is distinct from sibling tools like bootstrap_models (which starts the job) and others.

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

Usage Guidelines5/5

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

Explicitly tells the agent to poll after calling bootstrap_models, with a recommended interval of 2 minutes, and to report until status DONE or ERROR. Also explains the phase-based progress and reranker behavior.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yyy188/jama-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server