Skip to main content
Glama
ivossos

FCCS MCP Agentic Server

by ivossos

smart_retrieve_consolidation_breakdown

Retrieve consolidation dimension members for financial entities to analyze input, consolidation, totals, proportions, eliminations, and contributions in Oracle EPM FCCS.

Instructions

Retrieve all Consolidation dimension members (Entity Input, Entity Consolidation, Entity Total, Proportion, Elimination, Contribution) for an entity / Recuperar todos os membros da dimensao Consolidation para uma entidade

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountYesThe Account member (e.g., 'FCCS_Net Income')
entityNoThe Entity member (default: 'FCCS_Total Geography')
periodNoThe Period member (default: 'Jan')
yearsNoThe Years member (default: 'FY24')
scenarioNoThe Scenario member (default: 'Actual')

Implementation Reference

  • The main asynchronous handler function that implements the core logic of the smart_retrieve_consolidation_breakdown tool. It retrieves financial data for all consolidation dimension members (Entity Input, Consolidation, Total, Proportion, Elimination, Contribution) by making multiple data export calls.
    async def smart_retrieve_consolidation_breakdown(
        account: str,
        entity: str = "FCCS_Total Geography",
        period: str = "Jan",
        years: str = "FY24",
        scenario: str = "Actual"
    ) -> dict[str, Any]:
        """Retrieve all Consolidation dimension members for an entity / Recuperar todos os membros da dimensao Consolidation.
    
        This function retrieves FCCS_Entity Input, FCCS_Entity Consolidation, FCCS_Entity Total,
        FCCS_Proportion, FCCS_Elimination, and FCCS_Contribution for a given entity.
    
        Args:
            account: The Account member (e.g., 'FCCS_Net Income').
            entity: The Entity member (default: 'FCCS_Total Geography').
            period: The Period member (default: 'Jan').
            years: The Years member (default: 'FY24').
            scenario: The Scenario member (default: 'Actual').
    
        Returns:
            dict: The retrieved data for all Consolidation members.
        """
        consolidation_members = [
            "FCCS_Entity Input",
            "FCCS_Entity Consolidation",
            "FCCS_Entity Total",
            "FCCS_Proportion",
            "FCCS_Elimination",
            "FCCS_Contribution"
        ]
        
        results = {}
        for consol_member in consolidation_members:
            try:
                grid_definition = {
                    "suppressMissingBlocks": True,
                    "pov": {
                        "members": [
                            [years], [scenario], ["FCCS_YTD"], [consol_member],
                            ["FCCS_Intercompany Top"], ["FCCS_Total Data Source"],
                            ["FCCS_Mvmts_Total"], [entity], ["Entity Currency"],
                            ["Total Custom 3"], ["Total Region"], ["Total Venturi Entity"],
                            ["Total Custom 4"]
                        ]
                    },
                    "columns": [{"members": [[period]]}],
                    "rows": [{"members": [[account]]}]
                }
                result = await _client.export_data_slice(_app_name, "Consol", grid_definition)
                
                # Extract value from result
                value = 0.0
                if result and "rows" in result and len(result["rows"]) > 0:
                    row = result["rows"][0]
                    if "data" in row and len(row["data"]) > 0:
                        try:
                            value = float(row["data"][0])
                        except (ValueError, TypeError):
                            value = 0.0
                
                results[consol_member] = value
            except Exception as e:
                results[consol_member] = 0.0
        
        return {
            "status": "success",
            "data": {
                "entity": entity,
                "account": account,
                "period": period,
                "years": years,
                "scenario": scenario,
                "consolidation_breakdown": results,
                "summary": {
                    "entity_input": results.get("FCCS_Entity Input", 0.0),
                    "entity_consolidation": results.get("FCCS_Entity Consolidation", 0.0),
                    "entity_total": results.get("FCCS_Entity Total", 0.0),
                    "proportion": results.get("FCCS_Proportion", 0.0),
                    "elimination": results.get("FCCS_Elimination", 0.0),
                    "contribution": results.get("FCCS_Contribution", 0.0)
                }
            }
        }
  • The input schema definition for the smart_retrieve_consolidation_breakdown tool, defining parameters like account (required), entity, period, years, scenario with descriptions and types.
    {
        "name": "smart_retrieve_consolidation_breakdown",
        "description": "Retrieve all Consolidation dimension members (Entity Input, Entity Consolidation, Entity Total, Proportion, Elimination, Contribution) for an entity / Recuperar todos os membros da dimensao Consolidation para uma entidade",
        "inputSchema": {
            "type": "object",
            "properties": {
                "account": {
                    "type": "string",
                    "description": "The Account member (e.g., 'FCCS_Net Income')",
                },
                "entity": {
                    "type": "string",
                    "description": "The Entity member (default: 'FCCS_Total Geography')",
                },
                "period": {
                    "type": "string",
                    "description": "The Period member (default: 'Jan')",
                },
                "years": {
                    "type": "string",
                    "description": "The Years member (default: 'FY24')",
                },
                "scenario": {
                    "type": "string",
                    "description": "The Scenario member (default: 'Actual')",
                },
            },
            "required": ["account"],
        },
    },
  • Registration of the tool handler in the central TOOL_HANDLERS dictionary, mapping the tool name to the imported function from data module.
    "smart_retrieve_consolidation_breakdown": data.smart_retrieve_consolidation_breakdown,
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 this is a retrieval operation, implying read-only behavior, but doesn't disclose any behavioral traits like authentication requirements, rate limits, pagination, error handling, or what format the data returns in. For a tool with 5 parameters and no output schema, this leaves significant gaps.

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 concise and front-loaded with the English version first. The Portuguese translation adds redundancy but doesn't significantly harm readability. Both sentences directly contribute to stating the tool's purpose without unnecessary elaboration.

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 5 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't explain what the tool returns, how the consolidation dimension members are structured, or provide any behavioral context. The description alone leaves too many unanswered questions for effective tool invocation.

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 all parameters are documented in the schema. The description doesn't add any additional meaning about parameters beyond what's in the schema. It mentions 'entity' generically but doesn't elaborate on the parameter relationships or usage patterns. Baseline 3 is appropriate when the schema does 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 tool's purpose: retrieving consolidation dimension members for an entity. It specifies the resource (consolidation dimension members) and the scope (for an entity). However, it doesn't explicitly differentiate from sibling tools like 'smart_retrieve' or 'get_members', which appear to be related retrieval operations.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'smart_retrieve' or 'get_members', nor does it specify any prerequisites, exclusions, or contextual constraints for 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