Skip to main content
Glama
ivossos

FCCS MCP Agentic Server

by ivossos

get_job_status

Check the status of a specific job in Oracle EPM Cloud FCCS by providing its job ID.

Instructions

Get the status of a specific job / Obter o status de um job especifico

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
job_idYesThe ID of the job to check / O ID do job para verificar

Implementation Reference

  • The main tool handler function that executes the get_job_status logic by calling the FCCS client.
    async def get_job_status(job_id: str) -> dict[str, Any]:
        """Get the status of a specific job / Obter o status de um job especifico.
    
        Args:
            job_id: The ID of the job to check.
    
        Returns:
            dict: Job status details.
        """
        status = await _client.get_job_status(_app_name, job_id)
        return {"status": "success", "data": status}
  • The input schema definition for the get_job_status tool, specifying the required 'job_id' parameter.
    {
        "name": "get_job_status",
        "description": "Get the status of a specific job / Obter o status de um job especifico",
        "inputSchema": {
            "type": "object",
            "properties": {
                "job_id": {
                    "type": "string",
                    "description": "The ID of the job to check / O ID do job para verificar",
                },
            },
            "required": ["job_id"],
        },
    },
  • Registration of the get_job_status tool handler in the central TOOL_HANDLERS dictionary used by the agent.
    # Jobs
    "list_jobs": jobs.list_jobs,
    "get_job_status": jobs.get_job_status,
    "run_business_rule": jobs.run_business_rule,
    "run_data_rule": jobs.run_data_rule,
  • The FCCS client helper method invoked by the tool handler to retrieve job status from the REST API.
    async def get_job_status(self, app_name: str, job_id: str) -> dict[str, Any]:
        """Get job status / Obter status do trabalho."""
        if self.config.fccs_mock_mode:
            return MOCK_JOB_STATUS.get(
                job_id,
                {"jobId": job_id, "status": "Unknown", "details": "Mock job not found"}
            )
    
        response = await self._client.get(
            f"/{app_name}/jobs/{job_id}{self._get_query_params()}"
        )
        response.raise_for_status()
        return response.json()
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action is to 'get' status, implying a read-only operation, but doesn't clarify permissions needed, rate limits, error conditions, or what the status response includes (e.g., pending, completed, failed). This leaves significant gaps for an agent to understand behavioral traits.

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 brief and front-loaded with the core purpose in a single bilingual sentence (English/Portuguese). There's no wasted text, but the bilingual format slightly reduces efficiency for an English-only agent. It remains appropriately sized for a simple tool.

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

Completeness2/5

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

Given no annotations and no output schema, the description is incomplete for a tool that likely returns status details. It doesn't explain what status values to expect, error handling, or how this integrates with sibling tools like 'list_jobs'. For a status-checking tool in a job management context, more contextual information is needed.

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 description coverage is 100%, with the parameter 'job_id' documented as 'The ID of the job to check'. The description adds no additional meaning beyond this, such as format examples or sourcing instructions. Since the schema fully covers the parameter, the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'get' and resource 'status of a specific job', making the purpose evident. It distinguishes from siblings like 'list_jobs' (which lists multiple jobs) by specifying retrieval of a single job's status. However, it doesn't explicitly differentiate from 'get_report_job_status', which might handle a different job type.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like 'list_jobs' (for overview) or 'get_report_job_status' (for report-specific jobs). The description implies usage for checking a specific job's status but offers no context on prerequisites, timing, or exclusions.

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/ivossos/fccs-mcp-ag-server'

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