Skip to main content
Glama
yyy188
by yyy188

get_sync_progress

Poll the progress of a synchronization job until it finishes or fails, reporting status and progress.

Instructions

Poll the progress of an init, reinit or sync job.

After calling init_jama_project or reinit_jama_project, poll this roughly
every 2 minutes until status is DONE or ERROR, reporting each sample to the
user. For a project-wide view of all operations and their last runs, use
get_sync_status instead.

Returns:
    {"job_id","project_id","kind","status","progress","total","done",
     "message","started_at","finished_at"}
    status is one of PENDING | RUNNING | DONE | ERROR.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
job_idYes
Behavior4/5

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

No annotations provided; description covers polling behavior, return fields, and status values. Lacks permission details but adequate for a simple polling tool.

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?

Concise: 4 sentences with return fields listed. Front-loaded purpose, no wasted words.

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?

Complete for a single-param polling tool with no output schema: covers purpose, usage pattern, alternative, and return structure.

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 has 0% description coverage, but description implies job_id is from init/reinit. Does not explicitly document format or source, but context is sufficient.

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 tool polls progress of init/reinit/sync jobs. It specifies the verb 'poll', the resource 'progress', and distinguishes from get_sync_status.

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 says to poll every 2 minutes after specific calls until status is DONE or ERROR, and to report to user. Also names get_sync_status as alternative for project-wide view.

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