Skip to main content
Glama
ivossos

FCCS MCP Agentic Server

by ivossos

import_consolidation_rulesets

Import configurable consolidation rulesets into Oracle EPM Cloud FCCS to define financial consolidation processes and automate data integration tasks.

Instructions

Import configurable consolidation rulesets / Importar regras de consolidacao

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
parametersNoImport parameters

Implementation Reference

  • The main MCP tool handler function that executes the import_consolidation_rulesets logic by delegating to the FCCS client.
    async def import_consolidation_rulesets(
        parameters: Optional[dict[str, Any]] = None
    ) -> dict[str, Any]:
        """Import configurable consolidation rulesets / Importar regras de consolidacao.
    
        Args:
            parameters: Import parameters.
    
        Returns:
            dict: Job submission result.
        """
        result = await _client.import_consolidation_rulesets(_app_name, parameters)
        return {"status": "success", "data": result}
  • The input schema definition for the import_consolidation_rulesets tool within the TOOL_DEFINITIONS list.
    {
        "name": "import_consolidation_rulesets",
        "description": "Import configurable consolidation rulesets / Importar regras de consolidacao",
        "inputSchema": {
            "type": "object",
            "properties": {
                "parameters": {
                    "type": "object",
                    "description": "Import parameters",
                },
            },
        },
    },
  • Registration of consolidation tools, including import_consolidation_rulesets, in the central TOOL_HANDLERS dictionary.
    "export_consolidation_rulesets": consolidation.export_consolidation_rulesets,
    "import_consolidation_rulesets": consolidation.import_consolidation_rulesets,
    "validate_metadata": consolidation.validate_metadata,
    "generate_intercompany_matching_report": consolidation.generate_intercompany_matching_report,
    "import_supplementation_data": consolidation.import_supplementation_data,
    "deploy_form_template": consolidation.deploy_form_template,
    "generate_consolidation_process_report": consolidation.generate_consolidation_process_report,
  • Aggregation of all tool definitions including consolidation.TOOL_DEFINITIONS which contains the schema for import_consolidation_rulesets.
    ALL_TOOL_DEFINITIONS = (
        application.TOOL_DEFINITIONS +
        jobs.TOOL_DEFINITIONS +
        dimensions.TOOL_DEFINITIONS +
        journals.TOOL_DEFINITIONS +
        data.TOOL_DEFINITIONS +
        reports.TOOL_DEFINITIONS +
        consolidation.TOOL_DEFINITIONS +
        memo.TOOL_DEFINITIONS +
        feedback.TOOL_DEFINITIONS +
        local_data.TOOL_DEFINITIONS
    )
  • The underlying FCCSClient method called by the tool handler to perform the actual HTTP POST request for importing rulesets.
    async def import_consolidation_rulesets(
        self,
        app_name: str,
        parameters: Optional[dict[str, Any]] = None
    ) -> dict[str, Any]:
        """Import consolidation rulesets / Importar regras de consolidacao."""
        if self.config.fccs_mock_mode:
            return {"jobId": "302", "status": "Submitted", "jobType": "ImportRulesets"}
    
        response = await self._client.post(
            f"/{app_name}/importConfigConsolRules{self._get_query_params()}",
            json=parameters or {}
        )
        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 tool imports rulesets but doesn't describe what happens during import (e.g., overwrites existing rules, validates input, requires specific permissions). No information about side effects, error conditions, or performance characteristics is provided.

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 with bilingual duplication. The two language versions don't add value and could be condensed. However, it's not excessively verbose.

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 object parameter, the description is inadequate. It doesn't explain what consolidation rulesets are, what the import process entails, or what happens after import. The bilingual text doesn't compensate for these gaps.

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 documents the single 'parameters' object. The description adds no information about what parameters are expected, their format, or examples. Baseline 3 is appropriate when the schema does the heavy lifting, though the description could have provided context about typical parameter values.

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

Purpose2/5

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

The description states the tool imports consolidation rulesets, which is a specific verb+resource. However, it's vague about what 'import' entails (e.g., from where, to where, what format) and doesn't distinguish it from sibling tools like 'import_journals' or 'import_supplementation_data'. The bilingual phrasing adds no 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. It doesn't mention prerequisites, dependencies, or typical use cases. The bilingual text doesn't add any contextual information about usage scenarios.

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