Skip to main content
Glama
altrsoftware

ALTR MCP Server

Official
by altrsoftware

get_jobs

Read-only

Retrieve and filter classification jobs by status, type, or database to monitor their progress. Use after creating a job to check for completion.

Instructions

Check the status of classification jobs you've run.

Classification jobs run asynchronously and can take 10-30+ minutes to complete depending on your database size. Use this to check if a job has finished after waiting an appropriate amount of time.

Once a job shows status COMPLETED, you can fetch its detailed report with get_classification_report. If status is still RUNNING, wait longer before checking again.

Typical workflow: After creating a job with create_job, wait 15-30+ minutes, then use this function to check status. When status is COMPLETED, use the job_id with get_classification_report to view results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax jobs to return (default 50, max 50).
contiguous_idNoPagination token from a prior `get_jobs` call.
statusNoFilter by job status (e.g. RUNNING, PAUSED, COMPLETED, CANCELLED, FAILED).
job_typeNoFilter by job type (FULL, INCREMENTAL, RECLASSIFICATION).
database_idNoRestrict to a specific database (numeric ID from `get_databases` / `get_database_id`).
classification_typeNoOptional ALTR classification type code (1-5).
orderNoSort order by start time, `asc` or `desc` (default `desc`).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Annotations already provide `readOnlyHint: true`, so safety is clear. The description adds important behavioral context: jobs are asynchronous and take 10-30+ minutes. This is valuable beyond the annotation. 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and well-structured. It starts with the core purpose, then gives typical workflow and timing. Every sentence adds value, and the structure aids quick understanding.

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 tool's complexity (async job monitoring) and the presence of a complete input schema and output schema (mentioned implicitly), the description covers all necessary context: async nature, timing, workflow integration, and the next step.

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 coverage is 100%, so the schema itself fully documents all 7 parameters. The description does not need to add parameter details; baseline 3 is appropriate.

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's purpose: 'Check the status of classification jobs you've run.' It distinguishes itself from the sibling `get_classification_report` by explaining that this tool is for checking job status, and the report is fetched only after completion.

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?

The description provides explicit when-to-use guidance: after creating a job, wait 15-30+ minutes, then use this function. It also tells what to do when status is COMPLETED (use `get_classification_report`) and when still RUNNING (wait longer). No misleading advice.

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/altrsoftware/altr-mcp-server'

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