Skip to main content
Glama
yyy188
by yyy188

get_sync_status

Monitor sync operations for a Jama project, including current and recent init, reinit, and sync jobs, project status, and process metrics.

Instructions

Monitor a project's sync operations: current run + last run of each kind.

Use this to check on init_jama_project / reinit_jama_project / scheduled
sync for one project. It returns the in-flight job (if any), the most recent
init / reinit / sync job (terminal or running), the project's current state,
and lightweight process metrics. After starting an init or reinit, you may
poll this roughly every 2 minutes (reporting each sample to the user) until
active_job is null and the relevant recent.* entry is DONE/ERROR.

Args:
    project_id: Jama project id (numeric string, e.g. "20571").

Returns:
    {"project_id","project_status","last_sync_time","item_count",
     "chunk_count","active_job": {...}|null,
     "recent": {"init": {...}|null, "reinit": {...}|null,
                "sync": {...}|null},
     "process": {"rss_mb","threads","db_mb","chunks"}|null}
    Returns {"error": ...} if the project_id is not numeric or the server
    is not ready.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
Behavior4/5

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

No annotations are present, so the description carries full burden. It discloses return structure (active_job, recent jobs, process metrics) and error conditions (non-numeric project_id, server not ready). This is thorough for behavioral transparency.

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 fairly long but well-structured with sections for usage, parameters, and return format. It's not overly verbose and front-loads the purpose. Minor redundancy could be trimmed.

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?

Given no output schema, the description fully explains the return structure and error cases. It covers purpose, usage, parameters, and polling behavior, making it complete for an agent to use 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?

Schema coverage is 0% (only title), so description compensates by explaining project_id is a numeric string with example (e.g., '20571'). This adds meaning beyond the schema's type definition.

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 monitors sync operations, specifying 'current run + last run of each kind'. It uses a specific verb ('monitor') and resource ('sync operations'), distinguishing it from sibling tools like get_sync_progress.

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 explicitly states when to use (after init/reinit/sync) and provides polling instructions (every 2 minutes). It implies context but does not explicitly list when not to use or alternatives, though it's clear enough.

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