Skip to main content
Glama
ivossos

FCCS MCP Agentic Server

by ivossos

clear_data

Remove scenario-specific financial data for a given year and period in Oracle EPM Cloud FCCS to maintain system accuracy and prepare for new entries.

Instructions

Clear data for specified scenario, year, and period / Limpar dados

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scenarioNoScenario to clear
yearNoYear to clear
periodNoPeriod to clear

Implementation Reference

  • Primary MCP tool handler function for 'clear_data'. Builds parameters from optional inputs (scenario, year, period) and delegates to the underlying FCCS client method.
    async def clear_data(
        scenario: Optional[str] = None,
        year: Optional[str] = None,
        period: Optional[str] = None
    ) -> dict[str, Any]:
        """Clear data for specified scenario, year, and period / Limpar dados.
    
        Args:
            scenario: Scenario to clear.
            year: Year to clear.
            period: Period to clear.
    
        Returns:
            dict: Job submission result.
        """
        parameters = {}
        if scenario:
            parameters["scenario"] = scenario
        if year:
            parameters["year"] = year
        if period:
            parameters["period"] = period
    
        result = await _client.clear_data(_app_name, parameters)
        return {"status": "success", "data": result}
  • JSON schema definition for the 'clear_data' tool input validation, part of TOOL_DEFINITIONS list used by MCP.
    {
        "name": "clear_data",
        "description": "Clear data for specified scenario, year, and period / Limpar dados",
        "inputSchema": {
            "type": "object",
            "properties": {
                "scenario": {"type": "string", "description": "Scenario to clear"},
                "year": {"type": "string", "description": "Year to clear"},
                "period": {"type": "string", "description": "Period to clear"},
            },
        },
    },
  • Registration of the 'clear_data' tool handler in the central TOOL_HANDLERS dictionary, mapping name to data.clear_data function.
    "clear_data": data.clear_data,
  • Supporting client method in FccsClient that submits the CLEARDATA job to the FCCS REST API endpoint.
    async def clear_data(
        self,
        app_name: str,
        parameters: dict[str, Any]
    ) -> dict[str, Any]:
        """Clear data / Limpar dados."""
        if self.config.fccs_mock_mode:
            return {"jobId": "402", "status": "Submitted", "jobType": "ClearData"}
    
        payload = {"jobType": "CLEARDATA", **parameters}
        response = await self._client.post(
            f"/{app_name}/jobs{self._get_query_params()}",
            json=payload
        )
        response.raise_for_status()
        return response.json()
  • Inclusion of data.py TOOL_DEFINITIONS (containing clear_data schema) into the aggregated ALL_TOOL_DEFINITIONS for MCP server.
    data.TOOL_DEFINITIONS +
    reports.TOOL_DEFINITIONS +
    consolidation.TOOL_DEFINITIONS +
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. 'Clear data' implies a destructive operation, but it doesn't specify whether this is reversible, requires special permissions, has side effects on related data, or provides confirmation feedback. The description lacks critical details about what 'clear' means operationally (e.g., deletion, reset to defaults, archival).

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 includes redundant Portuguese translation that doesn't add functional value. The first sentence is front-loaded with the core action, but could be more structured (e.g., explaining consequences or typical use cases). The translation feels like clutter rather than helpful localization.

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 destructive tool with 3 parameters, no annotations, and no output schema, the description is inadequate. It doesn't address what happens after clearing (success confirmation, error handling), whether all three parameters are required, or how this interacts with sibling tools like 'get_journals' or 'update_journal_period'. The context suggests financial/consolidation data, but this isn't clarified.

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 parameters are documented in the schema. The description adds minimal value by listing the three parameters ('scenario, year, and period') but doesn't explain their relationships, valid values, or how they combine to identify data. No additional semantic context is provided beyond what's in the schema descriptions.

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

Purpose3/5

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

The description states the tool 'Clear data for specified scenario, year, and period' which provides a verb ('Clear') and resource ('data') with some specificity about parameters. However, it doesn't distinguish this from sibling tools like 'delete_data' (not present) or explain what type of data is being cleared (e.g., financial, journal, metadata). The Portuguese translation adds no functional 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. While siblings include data-related tools like 'export_data_slice' or 'import_journals', the description doesn't indicate whether this clears temporary data, resets configurations, or permanently deletes records. There's no mention of prerequisites, dependencies, or typical workflow context.

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