Skip to main content
Glama
ivossos

FCCS MCP Agentic Server

by ivossos

deploy_form_template

Deploy form templates in Oracle EPM Cloud FCCS to automate financial consolidation and close processes with specified parameters.

Instructions

Deploy a form template / Implantar um template de formulario

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
template_nameYesName of the form template to deploy
parametersNoDeployment parameters

Implementation Reference

  • The main tool handler function for 'deploy_form_template'. It wraps the FCCS client call to deploy the form template and formats the response.
    async def deploy_form_template(
        template_name: str,
        parameters: Optional[dict[str, Any]] = None
    ) -> dict[str, Any]:
        """Deploy a form template / Implantar um template de formulario.
    
        Args:
            template_name: Name of the form template to deploy.
            parameters: Deployment parameters.
    
        Returns:
            dict: Deployment result.
        """
        result = await _client.deploy_form_template(_app_name, template_name, parameters)
        return {"status": "success", "data": result}
  • JSON schema definition for the 'deploy_form_template' tool inputs, including required 'template_name' and optional 'parameters'.
    {
        "name": "deploy_form_template",
        "description": "Deploy a form template / Implantar um template de formulario",
        "inputSchema": {
            "type": "object",
            "properties": {
                "template_name": {
                    "type": "string",
                    "description": "Name of the form template to deploy",
                },
                "parameters": {
                    "type": "object",
                    "description": "Deployment parameters",
                },
            },
            "required": ["template_name"],
        },
    },
  • Registration of the 'deploy_form_template' tool handler in the main TOOL_HANDLERS dictionary, mapping the tool name to its implementation.
    "deploy_form_template": consolidation.deploy_form_template,
  • Underlying client method that performs the actual HTTP POST request to the FCCS API endpoint for deploying form templates.
    async def deploy_form_template(
        self,
        app_name: str,
        template_name: str,
        parameters: Optional[dict[str, Any]] = None
    ) -> dict[str, Any]:
        """Deploy form template / Implantar modelo de formulario."""
        if self.config.fccs_mock_mode:
            return {"templateName": template_name, "status": "Deployed"}
    
        payload = {"templateName": template_name, **(parameters or {})}
        response = await self._client.post(
            f"/{app_name}/formtemplates/{quote(template_name)}/actions/deploy{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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action ('deploy') without explaining what happens during deployment (e.g., whether it modifies system state, requires permissions, has side effects like data updates, or returns a result). For a tool with 'deploy' in its name—implying a potentially impactful operation—this is insufficient to inform the agent about risks or outcomes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is inefficiently structured with bilingual repetition ('Deploy a form template / Implantar um template de formulario'), which adds no value and wastes space. It's front-loaded but under-specified, failing to use its limited length to provide essential context. A single, clear English phrase would have been more concise and effective.

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 complexity implied by 'deploy' (likely a mutation), no annotations, no output schema, and a nested object parameter, the description is incomplete. It doesn't address what the tool returns, error conditions, or the scope of 'deployment' (e.g., to users, systems, or environments). For a tool with potential side effects, this leaves significant gaps in understanding its full 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 ('template_name' and 'parameters') adequately. The description adds no meaning beyond this, such as examples of deployment parameters or constraints on template names. With 2 parameters and high schema coverage, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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 action ('deploy') and resource ('form template'), which provides a basic understanding of purpose. However, it's vague about what 'deploy' entails (e.g., creating, activating, or distributing the template) and doesn't distinguish it from sibling tools like 'generate_report' or 'run_business_rule', which might involve similar form-related operations. The bilingual repetition adds no 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. The description doesn't mention prerequisites, context (e.g., after creating a template), or exclusions (e.g., not for editing templates). With many sibling tools for data processing and reporting, this lack of differentiation leaves the agent guessing about appropriate usage scenarios.

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