Skip to main content
Glama
ivossos

FCCS MCP Agentic Server

by ivossos

get_application_info

Retrieve FCCS application details from Oracle EPM Cloud for consolidation and close processes. Access configuration and status information to support financial reporting workflows.

Instructions

Get information about the FCCS application / Obter informacoes sobre a aplicacao FCCS

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function that executes the get_application_info tool by calling the FCCS client to retrieve applications and returning the data wrapped in a success response.
    async def get_application_info() -> dict[str, Any]:
        """Get information about the FCCS application / Obter informacoes sobre a aplicacao FCCS.
    
        Returns:
            dict: Application details including name, type, and description.
        """
        apps = await _client.get_applications()
        return {"status": "success", "data": apps}
  • The tool schema definition including name, description, and empty inputSchema (no parameters required). Part of TOOL_DEFINITIONS list.
    {
        "name": "get_application_info",
        "description": "Get information about the FCCS application / Obter informacoes sobre a aplicacao FCCS",
        "inputSchema": {
            "type": "object",
            "properties": {},
        },
    },
  • Registration of the tool handler in the central TOOL_HANDLERS dictionary, mapping the tool name to the implementation function.
    "get_application_info": application.get_application_info,
    "get_rest_api_version": application.get_rest_api_version,
  • Collection of all tool definitions including this one from application.TOOL_DEFINITIONS for the MCP server.
    ALL_TOOL_DEFINITIONS = (
        application.TOOL_DEFINITIONS +
        jobs.TOOL_DEFINITIONS +
        dimensions.TOOL_DEFINITIONS +
        journals.TOOL_DEFINITIONS +
        data.TOOL_DEFINITIONS +
        reports.TOOL_DEFINITIONS +
        consolidation.TOOL_DEFINITIONS +
        memo.TOOL_DEFINITIONS +
        feedback.TOOL_DEFINITIONS +
        local_data.TOOL_DEFINITIONS
    )
  • Helper function to set the global FCCS client instance used by the tool handler.
    def set_client(client: FccsClient):
        """Set the FCCS client instance."""
        global _client
        _client = client
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 implies a read-only operation ('Get information'), but does not specify permissions, rate limits, or response format. This is inadequate for a tool with zero annotation coverage.

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 and front-loaded, but includes redundant bilingual text ('Obter informacoes sobre a aplicacao FCCS') that adds no value for an AI agent. This reduces efficiency without improving clarity.

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 no annotations and no output schema, the description is incomplete. It fails to explain what information is returned (e.g., version, status, configuration) or behavioral aspects, making it insufficient for effective tool use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and schema description coverage is 100%, so no parameter information is needed. The description does not add or detract from parameter semantics, meeting the baseline for tools with no parameters.

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 'Get' and the resource 'information about the FCCS application', making the purpose understandable. However, it does not differentiate from siblings like 'get_dimensions' or 'get_journals' beyond specifying the application itself, which is a minor gap.

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, such as for retrieving general application metadata versus specific data from other tools. The description lacks context on prerequisites or exclusions, leaving usage unclear.

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