Skip to main content
Glama
ivossos

FCCS MCP Agentic Server

by ivossos

import_journals

Import consolidation journals into Oracle EPM Cloud FCCS to manage financial consolidation and close processes.

Instructions

Import consolidation journals / Importar diarios de consolidacao

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
parametersNoImport parameters

Implementation Reference

  • The main handler function for the 'import_journals' MCP tool. It calls the underlying FCCS client to submit an import journals job and wraps the result in a success response.
    async def import_journals(
        parameters: Optional[dict[str, Any]] = None
    ) -> dict[str, Any]:
        """Import consolidation journals / Importar diarios de consolidacao.
    
        Args:
            parameters: Import parameters.
    
        Returns:
            dict: Job submission result.
        """
        result = await _client.import_journals(_app_name, parameters)
        return {"status": "success", "data": result}
  • The input schema definition for the 'import_journals' tool, specifying an optional 'parameters' object.
    {
        "name": "import_journals",
        "description": "Import consolidation journals / Importar diarios de consolidacao",
        "inputSchema": {
            "type": "object",
            "properties": {
                "parameters": {"type": "object", "description": "Import parameters"},
            },
        },
    },
  • Registration of the 'import_journals' handler in the central TOOL_HANDLERS dictionary used by the agent to dispatch tool calls.
    "import_journals": journals.import_journals,
  • Inclusion of journals.TOOL_DEFINITIONS (containing the schema) into the aggregated ALL_TOOL_DEFINITIONS list exposed to MCP.
    journals.TOOL_DEFINITIONS +
  • Underlying client method that performs the actual HTTP POST to FCCS /jobs endpoint with jobType 'IMPORTJOURNALS', called by the tool handler.
    async def import_journals(
        self,
        app_name: str,
        parameters: Optional[dict[str, Any]] = None
    ) -> dict[str, Any]:
        """Import journals / Importar lancamentos."""
        if self.config.fccs_mock_mode:
            return {"jobId": "602", "status": "Submitted", "jobType": "ImportJournals"}
    
        payload = {"jobType": "IMPORTJOURNALS", **(parameters or {})}
        response = await self._client.post(
            f"/{app_name}/jobs{self._get_query_params()}",
            json=payload
        )
        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 full burden for behavioral disclosure. It mentions 'import' which implies a write/mutation operation, but doesn't specify permissions required, whether it's idempotent, what happens on failure, or any side effects. For a tool that likely modifies data, this is insufficient behavioral context.

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 bilingual repetition ('Import consolidation journals / Importar diarios de consolidacao') adds unnecessary length without value. However, it's still brief overall. The structure could be improved by front-loading the English version and optionally including translation, rather than presenting both equally.

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?

For a tool with no annotations, no output schema, and a nested parameters object, the description is inadequate. It doesn't explain what 'consolidation journals' are, what format they should be in, what the import process entails, or what success/failure looks like. Given the complexity implied by the sibling tools in this financial/consolidation domain, more context 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%, so the schema already documents the single 'parameters' object. The description adds no information about what specific parameters are needed, their format, or examples. With high schema coverage, the baseline is 3 even without parameter details in the description.

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 imports consolidation journals, which is a clear verb+resource combination. However, it doesn't differentiate from sibling tools like 'import_consolidation_rulesets' or 'import_supplementation_data' - all are import operations but for different resources. The bilingual phrasing adds redundancy without clarifying purpose.

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 about when to use this tool versus alternatives. There's no mention of prerequisites, timing considerations, or relationship to sibling tools like 'export_journals' or 'get_journals'. The description offers only the basic function without context for appropriate usage.

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