Skip to main content
Glama
ivossos

FCCS MCP Agentic Server

by ivossos

export_journals

Export consolidation journals from Oracle EPM Cloud FCCS for financial reporting and compliance needs. This tool retrieves journal data using specified parameters to support close processes.

Instructions

Export consolidation journals / Exportar diarios de consolidacao

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
parametersNoExport parameters

Implementation Reference

  • The MCP tool handler function for export_journals. It invokes the FCCS client method with app_name and parameters, wraps the result in a success dict.
    async def export_journals(
        parameters: Optional[dict[str, Any]] = None
    ) -> dict[str, Any]:
        """Export consolidation journals / Exportar diarios de consolidacao.
    
        Args:
            parameters: Export parameters (scenario, year, period, etc.).
    
        Returns:
            dict: Job submission result.
        """
        result = await _client.export_journals(_app_name, parameters)
        return {"status": "success", "data": result}
  • The input schema definition for the export_journals tool in TOOL_DEFINITIONS list.
    {
        "name": "export_journals",
        "description": "Export consolidation journals / Exportar diarios de consolidacao",
        "inputSchema": {
            "type": "object",
            "properties": {
                "parameters": {"type": "object", "description": "Export parameters"},
            },
        },
    },
  • Registration of the export_journals handler in the central TOOL_HANDLERS dictionary.
    "export_journals": journals.export_journals,
  • The underlying FCCSClient method that performs the actual API POST request to submit the export journals job.
    async def export_journals(
        self,
        app_name: str,
        parameters: Optional[dict[str, Any]] = None
    ) -> dict[str, Any]:
        """Export journals / Exportar lancamentos."""
        if self.config.fccs_mock_mode:
            return {"jobId": "601", "status": "Submitted", "jobType": "ExportJournals"}
    
        payload = {"jobType": "EXPORTJOURNALS", **(parameters or {})}
        response = await self._client.post(
            f"/{app_name}/jobs{self._get_query_params()}",
            json=payload
        )
        response.raise_for_status()
        return response.json()
  • Aggregation of tool definitions including the export_journals schema into ALL_TOOL_DEFINITIONS.
    journals.TOOL_DEFINITIONS +
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action ('export') without detailing whether this is a read-only operation, if it requires specific permissions, what happens during export (e.g., file generation, data transformation), or any side effects like rate limits or system impact. This is inadequate for a tool with potential data access implications.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is brief but inefficiently structured due to bilingual repetition ('Export consolidation journals / Exportar diarios de consolidacao'), which adds no value. It is front-loaded with the core action but wastes space on redundancy rather than providing useful information. A single, clear phrase would be more effective.

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 the tool's complexity (involving data export with nested parameters) and lack of annotations or output schema, the description is insufficient. It does not explain what the export produces (e.g., file format, content), how results are delivered, or any behavioral nuances. For a tool that likely handles sensitive financial data, this leaves critical gaps in understanding.

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?

The input schema has 100% description coverage, with one parameter object described as 'Export parameters'. The description adds no additional semantic context about what these parameters might include (e.g., date ranges, filters, formats). Since schema coverage is high, the baseline score of 3 applies, but the description does not compensate with any meaningful parameter details.

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

Purpose3/5

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

The description states the tool exports 'consolidation journals' or 'diarios de consolidacao', which provides a basic verb+resource combination. However, it lacks specificity about what format the export is in, what scope it covers, or how it differs from sibling tools like 'export_data_slice' or 'export_consolidation_rulesets'. The bilingual phrasing adds redundancy without enhancing clarity.

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. With multiple export-related siblings (export_data_slice, export_consolidation_rulesets), the description fails to indicate whether this is for bulk exports, specific formats, or particular use cases. There is no mention of prerequisites, dependencies, or typical scenarios for invocation.

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