Skip to main content
Glama
ivossos

FCCS MCP Agentic Server

by ivossos

export_data_slice

Export specific data slices or grids from Oracle EPM Cloud FCCS for analysis and reporting purposes.

Instructions

Export a specific data slice (grid) from the application / Exportar um slice de dados

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cube_nameNoThe name of the cube (default: 'Consol')
grid_definitionYesThe data grid definition with pov, columns, and rows

Implementation Reference

  • The main handler function for the 'export_data_slice' tool. It takes a grid definition and optional cube name, calls the underlying FCCS client to export the data slice, and returns the result wrapped in a success status.
    async def export_data_slice(
        grid_definition: dict[str, Any],
        cube_name: str = "Consol"
    ) -> dict[str, Any]:
        """Export a specific data slice (grid) from the application / Exportar um slice de dados.
    
        Args:
            grid_definition: The data grid definition with pov, columns, and rows.
            cube_name: The name of the cube (default: 'Consol').
    
        Returns:
            dict: The exported data slice with rows and column values.
        """
        result = await _client.export_data_slice(_app_name, cube_name, grid_definition)
        return {"status": "success", "data": result}
  • The input schema definition for the 'export_data_slice' tool, specifying the expected parameters: grid_definition (required) and optional cube_name.
    {
        "name": "export_data_slice",
        "description": "Export a specific data slice (grid) from the application / Exportar um slice de dados",
        "inputSchema": {
            "type": "object",
            "properties": {
                "cube_name": {
                    "type": "string",
                    "description": "The name of the cube (default: 'Consol')",
                },
                "grid_definition": {
                    "type": "object",
                    "description": "The data grid definition with pov, columns, and rows",
                },
            },
            "required": ["grid_definition"],
        },
    },
  • The TOOL_HANDLERS dictionary in the agent registers 'export_data_slice' by mapping the tool name to its handler function data.export_data_slice. This is used by the execute_tool function to dispatch calls.
    TOOL_HANDLERS = {
        # Application
        "get_application_info": application.get_application_info,
        "get_rest_api_version": application.get_rest_api_version,
        # Jobs
        "list_jobs": jobs.list_jobs,
        "get_job_status": jobs.get_job_status,
        "run_business_rule": jobs.run_business_rule,
        "run_data_rule": jobs.run_data_rule,
        # Dimensions
        "get_dimensions": dimensions.get_dimensions,
        "get_members": dimensions.get_members,
        "get_dimension_hierarchy": dimensions.get_dimension_hierarchy,
        # Journals
        "get_journals": journals.get_journals,
        "get_journal_details": journals.get_journal_details,
        "perform_journal_action": journals.perform_journal_action,
        "update_journal_period": journals.update_journal_period,
        "export_journals": journals.export_journals,
        "import_journals": journals.import_journals,
        # Data
        "export_data_slice": data.export_data_slice,
        "smart_retrieve": data.smart_retrieve,
        "smart_retrieve_consolidation_breakdown": data.smart_retrieve_consolidation_breakdown,
        "smart_retrieve_with_movement": data.smart_retrieve_with_movement,
        "copy_data": data.copy_data,
        "clear_data": data.clear_data,
        # Reports
        "generate_report": reports.generate_report,
        "get_report_job_status": reports.get_report_job_status,
        "generate_report_script": reports.generate_report_script,
        # Consolidation
        "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,
        # Memo
        "generate_system_pitch": memo.generate_system_pitch,
        "generate_investment_memo": memo.generate_investment_memo,
        # Feedback
        "submit_feedback": feedback.submit_feedback,
        "get_recent_executions": feedback.get_recent_executions,
        # Local Data
        "query_local_metadata": local_data.query_local_metadata,
    }
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 exports data but doesn't mention whether this is a read-only operation, if it requires specific permissions, what format the export is in (e.g., CSV, PDF), or any rate limits. This leaves significant gaps in understanding the tool's behavior beyond its basic function.

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 brief and front-loaded with the core action and resource in a single bilingual sentence. There's no wasted text, but the bilingual repetition ('Export a specific data slice (grid) from the application / Exportar um slice de dados') slightly reduces efficiency without adding new information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 tool with nested object parameters for data export, the description is minimally adequate. It covers the basic purpose but lacks details on behavior, output format, or error handling. For a data export tool with complexity, this leaves room for improvement in providing a complete context.

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 both parameters ('cube_name' and 'grid_definition') with descriptions. The tool description adds no additional meaning about parameters, such as examples of grid definitions or cube usage, but doesn't need to compensate for low coverage. Baseline 3 is appropriate as the schema handles the heavy lifting.

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 action ('Export') and the resource ('specific data slice (grid)'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'export_consolidation_rulesets' or 'export_journals', which also export data but different types. The bilingual format adds clarity but doesn't enhance differentiation.

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 'smart_retrieve' or 'generate_report', which might retrieve or output data differently. The description lacks context about use cases, prerequisites, or exclusions, leaving the agent to infer usage from the tool name alone.

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