Skip to main content
Glama
yyy188
by yyy188

init_jama_project

Initialize a Jama project by downloading, cleaning, vectorizing, and indexing its items. Returns a job ID for async progress tracking.

Instructions

Initialize a Jama project: download, clean, vectorize and index its items.

Runs as an async background task and returns a job_id immediately so the
caller (LLM) is never blocked. Poll progress with get_sync_progress roughly
every 2 minutes until status is DONE or ERROR, reporting each sample to the
user. To re-index a project that is already initialized, prefer
reinit_jama_project.

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

Returns:
    {"job_id": "...", "project_id": ..., "status": "RUNNING"}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
Behavior4/5

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

No annotations provided, but description clearly explains async behavior and polling requirement. Could mention potential side effects or failure modes, but overall adequate.

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, front-loaded with purpose. Every sentence adds value: async note, polling instructions, sibling tool advice, args and returns. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose, behavior, parameters, and return format. Lacks prerequisites (e.g., project must exist) but sufficient for a single-parameter async tool with no output schema.

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

Parameters5/5

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

Adds beyond schema: describes project_id as 'numeric string' with example '20571'. Schema only defines type string. Description provides format and usage context.

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?

States 'Initialize a Jama project: download, clean, vectorize and index its items', which is a specific verb-resource pair. Differentiates from sibling reinit_jama_project by explicitly advising its use for already initialized projects.

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?

Provides explicit instructions: runs async, returns job_id, poll with get_sync_progress every 2 minutes, report samples to user. Also tells when to use sibling reinit_jama_project instead.

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