Skip to main content
Glama
ivossos

FCCS MCP Agentic Server

by ivossos

export_consolidation_rulesets

Export configurable consolidation rulesets from Oracle EPM Cloud FCCS to manage financial consolidation processes and rule configurations.

Instructions

Export configurable consolidation rulesets / Exportar regras de consolidacao

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
parametersNoExport parameters (ruleNames, rulesetNames, etc.)

Implementation Reference

  • The primary handler function for the 'export_consolidation_rulesets' tool. It invokes the FCCS client method with the application name and parameters, wrapping the result in a success response.
    async def export_consolidation_rulesets(
        parameters: Optional[dict[str, Any]] = None
    ) -> dict[str, Any]:
        """Export configurable consolidation rulesets / Exportar regras de consolidacao.
    
        Args:
            parameters: Export parameters (ruleNames, rulesetNames, etc.).
    
        Returns:
            dict: Job submission result.
        """
        result = await _client.export_consolidation_rulesets(_app_name, parameters)
        return {"status": "success", "data": result}
  • The input schema definition for the 'export_consolidation_rulesets' tool, defining an optional 'parameters' object.
    {
        "name": "export_consolidation_rulesets",
        "description": "Export configurable consolidation rulesets / Exportar regras de consolidacao",
        "inputSchema": {
            "type": "object",
            "properties": {
                "parameters": {
                    "type": "object",
                    "description": "Export parameters (ruleNames, rulesetNames, etc.)",
                },
            },
        },
    },
  • Registration of the tool handler in the central TOOL_HANDLERS dictionary used by the agent to dispatch tool calls.
    "export_consolidation_rulesets": consolidation.export_consolidation_rulesets,
  • The FCCS client helper method that makes the actual API request to export consolidation rulesets from the FCCS application.
    async def export_consolidation_rulesets(
        self,
        app_name: str,
        parameters: Optional[dict[str, Any]] = None
    ) -> dict[str, Any]:
        """Export consolidation rulesets / Exportar regras de consolidacao."""
        if self.config.fccs_mock_mode:
            return {"jobId": "301", "status": "Submitted", "jobType": "ExportRulesets"}
    
        payload = parameters or {}
        if not payload.get("ruleNames") and not payload.get("rulesetNames"):
            return {
                "status": "Parameter Required",
                "message": "Consolidation ruleset export requires specific rule names.",
                "suggestion": "Provide 'ruleNames' or 'rulesetNames' in parameters."
            }
    
        response = await self._client.post(
            f"/{app_name}/exportConfigConsolRules{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. 'Export' implies a read operation that produces output, but the description doesn't specify what gets exported (file format, structure), whether it requires specific permissions, if it's a synchronous or asynchronous operation, or what happens on failure. For a tool with no annotation coverage, this leaves significant behavioral questions unanswered.

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 extremely concise with just two phrases (English and Portuguese translation). While this is efficient, the Portuguese translation adds no functional value and represents wasted space. The English portion is front-loaded with the core purpose, but could benefit from more substantive content given the tool's likely complexity.

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 nested parameter object, the description is inadequate. It doesn't explain what 'consolidation rulesets' are, what format they export in, whether this is a bulk operation, or what the expected output looks like. For a tool that presumably handles complex financial consolidation rules, this leaves too many contextual gaps for effective agent use.

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 the single 'parameters' object documented as 'Export parameters (ruleNames, rulesetNames, etc.)'. The description adds no parameter information beyond what the schema provides. With high schema coverage, the baseline score of 3 is appropriate - the schema does the heavy lifting, and the description doesn't compensate with additional parameter context.

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 'Export configurable consolidation rulesets' restates the tool name 'export_consolidation_rulesets' with minimal additional information. It provides a basic verb+resource combination but lacks specificity about what 'export' means in this context (e.g., file format, destination). The Portuguese translation adds no functional clarity. It doesn't distinguish from sibling tools like 'export_data_slice' or 'export_journals' beyond the resource type.

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

Usage Guidelines1/5

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

The description provides no guidance on when to use this tool versus alternatives. There's no mention of prerequisites, typical use cases, or comparison to sibling tools like 'import_consolidation_rulesets' or 'generate_consolidation_process_report'. The agent receives no help in determining when this export operation is appropriate versus other export or reporting tools.

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