Skip to main content
Glama

Tribal: Check Ingest Job Status

tribal_job_status

Check the progress of an ingest job and retrieve its completion status, with optional blocking until the job finishes.

Instructions

Check the progress of an ingest job submitted via tribal_ingest.

Job lifecycle: queued → extracting → triaging → relating → completed/failed

Terminal states:

  • "completed": Pipeline ran to conclusion. Check outcome for details:

    • "success": All candidates triaged successfully and relations committed.

    • "partial": Some triage tasks failed permanently; the relation task ran on a subset.

    • "empty": Relation task ran with zero items to relate (all duplicates or all triage failures). If tasks_failed > 0, the pipeline likely failed at triage; treat as degraded rather than "nothing new".

  • "failed": Pipeline could not complete. outcome = "failure". Check error context.

Set wait_seconds to block until the job completes or the timeout expires. This collapses ingest + poll into a single round-trip for fast operations. With wait_seconds=0 (default), returns immediately with current status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
job_idYesJob ID returned by tribal_ingest.
wait_secondsNoIf > 0, the server blocks until the job reaches a final status (completed or failed) or the timeout expires, whichever comes first. Returns current status either way. Use this to collapse ingest + poll into fewer round-trips for fast operations.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
batch_sizeNoNumber of knowledge candidates extracted. Set after extraction completes.
created_atYes
items_createdYesNew knowledge items stored (novel content).
job_idYes
observations_createdYesDuplicate observations recorded (strengthens existing items).
outcomeNoFinal result. Only set when status is 'completed' or 'failed'.
statusYesCurrent lifecycle state.
tasks_completedYesTriage tasks completed successfully.
tasks_failedYesTriage tasks that failed permanently.
updated_atYes
Behavior5/5

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

With no annotations, the description fully covers behavioral traits: job lifecycle (queued → extracting → triaging → relating → completed/failed), terminal states (completed, failed, with sub-outcomes), and wait_seconds blocking behavior. No contradictions.

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-organized with sections for lifecycle, terminal states, and usage. It is somewhat lengthy but all information is relevant and earns its place.

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 the output schema exists (not shown), the description need not detail return format. It comprehensively covers job lifecycle, terminal states, and wait_seconds behavior, leaving no gaps for agent understanding.

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 100%, so baseline is 3. The description adds value by explaining the job lifecycle and the effect of wait_seconds beyond schema descriptions, but the schema already describes parameters adequately.

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 that the tool checks the progress of an ingest job submitted via tribal_ingest, with a specific verb ('Check') and resource ('Ingest Job Status'). It distinguishes from sibling tools by focusing on status polling.

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?

Guidance is provided on when to use (after tribal_ingest) and how to use wait_seconds to collapse round-trips. It does not explicitly mention when not to use or alternative tools, but the context is clear.

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/tribal-memory/tribal'

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