Skip to main content
Glama
ivossos

FCCS MCP Agentic Server

by ivossos

get_journals

Retrieve consolidation journals from Oracle EPM Cloud FCCS by applying filters for scenario, year, period, status, and other parameters to access financial data.

Instructions

Retrieve consolidation journals with optional filters / Obter diarios de consolidacao

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scenarioYesFilter by scenario (required, e.g., 'Actual')
yearYesFilter by year (required, e.g., 'FY25')
periodYesFilter by period (required, e.g., 'Jan', 'Feb', 'Mar')
consolidationNoFilter by consolidation member (default: 'FCCS_Entity Input')FCCS_Entity Input
viewNoFilter by view (default: 'FCCS_Periodic')FCCS_Periodic
statusNoFilter by status (default: 'Posted'). Valid: 'Working', 'Submitted', 'Approved', 'Rejected', 'Posted'Posted
offsetNoOffset for pagination (default: 0)
limitNoLimit results (default: 100)

Implementation Reference

  • The primary handler function for the 'get_journals' tool. It accepts input parameters, constructs filters, invokes the FCCS client method, and formats the response.
    async def get_journals(
        scenario: str,
        year: str,
        period: str,
        consolidation: str = "FCCS_Entity Input",
        view: str = "FCCS_Periodic",
        status: str = "Posted",
        offset: int = 0,
        limit: int = 100
    ) -> dict[str, Any]:
        """Retrieve consolidation journals with filters / Obter diarios de consolidacao.
    
        Note: FCCS REST API requires scenario, year, period, consolidation, view, and status.
    
        Args:
            scenario: Filter by scenario (required, e.g., 'Actual').
            year: Filter by year (required, e.g., 'FY25').
            period: Filter by period (required, e.g., 'Jan', 'Feb', 'Mar').
            consolidation: Filter by consolidation member (default: 'FCCS_Entity Input').
            view: Filter by view (default: 'FCCS_Periodic').
            status: Filter by status (default: 'Posted'). Valid: 'Working', 'Submitted', 'Approved', 'Rejected', 'Posted'.
            offset: Offset for pagination (default: 0).
            limit: Limit results (default: 100).
    
        Returns:
            dict: List of journals.
        """
        filters = {
            "scenario": scenario,
            "year": year,
            "period": period,
            "consolidation": consolidation,
            "view": view,
            "status": status,
        }
    
        journals = await _client.get_journals(
            _app_name, filters, offset, limit
        )
        return {"status": "success", "data": journals}
  • The input schema and metadata definition for the 'get_journals' tool, including properties, descriptions, defaults, and required fields.
        "name": "get_journals",
        "description": "Retrieve consolidation journals with optional filters / Obter diarios de consolidacao",
        "inputSchema": {
            "type": "object",
            "properties": {
                "scenario": {"type": "string", "description": "Filter by scenario (required, e.g., 'Actual')"},
                "year": {"type": "string", "description": "Filter by year (required, e.g., 'FY25')"},
                "period": {"type": "string", "description": "Filter by period (required, e.g., 'Jan', 'Feb', 'Mar')"},
                "consolidation": {"type": "string", "description": "Filter by consolidation member (default: 'FCCS_Entity Input')", "default": "FCCS_Entity Input"},
                "view": {"type": "string", "description": "Filter by view (default: 'FCCS_Periodic')", "default": "FCCS_Periodic"},
                "status": {"type": "string", "description": "Filter by status (default: 'Posted'). Valid: 'Working', 'Submitted', 'Approved', 'Rejected', 'Posted'", "default": "Posted"},
                "offset": {"type": "number", "description": "Offset for pagination (default: 0)"},
                "limit": {"type": "number", "description": "Limit results (default: 100)"},
            },
            "required": ["scenario", "year", "period"],
        },
    },
  • Maps the tool name 'get_journals' to its handler function in the central TOOL_HANDLERS registry used by the agent.
    "get_journals": journals.get_journals,
  • The low-level FCCSClient method that performs the actual API call to retrieve journals, used by the tool handler.
    async def get_journals(
        self,
        app_name: str,
        filters: Optional[dict[str, str]] = None,
        offset: int = 0,
        limit: int = 100
    ) -> dict[str, Any]:
        """Get journals / Obter lancamentos."""
        if self.config.fccs_mock_mode:
            return {"items": [], "offset": offset, "limit": limit, "count": 0}
    
        # Build query parameters
        params = {"offset": offset, "limit": limit}
        
        if filters:
            # Build the q parameter as a JSON-like string
            filter_parts = []
            for key in ["scenario", "year", "period", "status", "consolidation", "view", "entity", "group", "label", "description"]:
                if key in filters:
                    filter_parts.append(f'"{key}":"{filters[key]}"')
            if filter_parts:
                # Use proper JSON format for the q parameter
                params["q"] = "{" + ",".join(filter_parts) + "}"
    
        # Use httpx params to handle URL encoding automatically
        response = await self._client.get(
            f"/{app_name}/journals",
            params=params
        )
    
        if response.status_code == 200:
            data = response.json()
            if not data.get("items"):
                data["message"] = "No journals currently exist in the system."
            return data
    
        # Return error details if not 200
        return {
            "items": [],
            "offset": offset,
            "limit": limit,
            "count": 0,
            "error": f"HTTP {response.status_code}",
            "detail": response.text[:500] if response.text else "No response body"
        }
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 mentions retrieval with filters but fails to describe critical behaviors like pagination handling (implied by offset/limit parameters), authentication needs, rate limits, or what the return format looks like. This is a significant gap for a tool with 8 parameters.

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 a single, efficient sentence that states the core purpose without unnecessary elaboration. However, the bilingual repetition ('Obter diarios de consolidacao') adds minor redundancy, preventing a perfect score.

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 the tool's complexity (8 parameters, no output schema, no annotations), the description is inadequate. It lacks details on behavioral traits, output format, error handling, and usage context, leaving significant gaps for an AI agent to understand how to invoke it correctly.

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 all parameters thoroughly with descriptions, defaults, and required status. The description adds no additional meaning beyond implying filtering, which is already covered in the schema. 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 verb ('Retrieve') and resource ('consolidation journals'), and mentions optional filters, which gives a specific purpose. However, it doesn't explicitly differentiate from sibling tools like 'export_journals' or 'get_journal_details', which would require a 5.

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 such as 'export_journals' or 'get_journal_details', nor does it mention any prerequisites or exclusions. It only states what the tool does, not when to apply it.

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