Skip to main content
Glama
ivossos

FCCS MCP Agentic Server

by ivossos

list_jobs

Retrieve recent job listings from Oracle EPM Cloud Financial Consolidation and Close (FCCS) applications to monitor processing status and track system activities.

Instructions

List recent jobs in the FCCS application / Listar jobs recentes na aplicacao FCCS

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function for the 'list_jobs' MCP tool. It asynchronously calls the FCCS client to retrieve recent jobs and wraps the result in a standard response format.
    async def list_jobs() -> dict[str, Any]:
        """List recent jobs in the FCCS application / Listar jobs recentes na aplicacao FCCS.
    
        Returns:
            dict: List of recent jobs with status information.
        """
        jobs = await _client.list_jobs(_app_name)
        return {"status": "success", "data": jobs}
  • The input schema definition for the 'list_jobs' tool, specifying no required parameters as an empty object.
    {
        "name": "list_jobs",
        "description": "List recent jobs in the FCCS application / Listar jobs recentes na aplicacao FCCS",
        "inputSchema": {
            "type": "object",
            "properties": {},
        },
    },
  • Registration of the 'list_jobs' tool handler in the central TOOL_HANDLERS dictionary used by the agent to dispatch tool calls.
    "list_jobs": jobs.list_jobs,
  • Inclusion of job tools' schema definitions (including list_jobs) into the complete ALL_TOOL_DEFINITIONS list exposed to the MCP server.
    jobs.TOOL_DEFINITIONS +
Behavior2/5

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

With no annotations, the description carries full burden but only states the action without behavioral details. It doesn't disclose whether this is read-only, paginated, rate-limited, or what 'recent' means (e.g., time range, count). This leaves significant gaps for a tool with potential data retrieval implications.

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 front-loaded and efficient with two parallel language phrases, though the Portuguese translation adds redundancy without extra value. It avoids unnecessary elaboration but could be more streamlined.

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, no output schema, and a list operation that likely returns structured data, the description is incomplete. It doesn't explain return values, format, or behavioral traits, leaving the agent with insufficient context for reliable use.

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?

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description adds no parameter information, which is acceptable here, but doesn't compensate for any gaps since none exist.

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 ('List') and resource ('recent jobs in the FCCS application'), with a Portuguese translation adding clarity for bilingual contexts. It distinguishes from siblings like 'get_job_status' (status check) and 'get_recent_executions' (executions vs. jobs), though not explicitly named.

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 'get_recent_executions' or 'get_job_status'. The description implies it lists recent jobs, but lacks context on frequency, scope, or prerequisites for use.

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