Skip to main content
Glama
yogeshkulkarni553

Content Server

uploadContentFileAboutOrganization

Upload organizational content files to the Content Server for storage and management.

Instructions

Upload content file about the organization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileYesThe file content to upload
fileNameYesThe file name
roleNoThe roles of the user

Implementation Reference

  • The core handler function for the MCP tool 'uploadContentFileAboutOrganization'. It receives file content, name, and optional role, delegates the upload to RagService.upload_file using the user ID from environment, and returns a success message.
    def upload_content_file_about_organization(self, file: str, file_name: str, role: str = "") -> list[str]:
        """
        Upload content file about the organization.
    
        Args:
            file: The file content to upload
            file_name: The file name (required)
            role: The roles of the user
    
        Returns:
            Success message
        """
        self.rag_service.upload_file(file, file_name, role, self.user_id_from_environment)
        return ["File uploaded successfully"]
  • mcp_server.py:88-110 (registration)
    Tool registration in the MCP server's list_tools handler, defining the tool name, description, and input schema with required 'file' and 'fileName' parameters.
    types.Tool(
        name="uploadContentFileAboutOrganization",
        description="Upload content file about the organization",
        inputSchema={
            "type": "object",
            "properties": {
                "file": {
                    "type": "string",
                    "description": "The file content to upload"
                },
                "fileName": {
                    "type": "string",
                    "description": "The file name"
                },
                "role": {
                    "type": "string",
                    "description": "The roles of the user"
                }
            },
            "required": ["file", "fileName"],
            "additionalProperties": False
        }
    ),
  • Input schema definition for the tool, specifying properties and requirements for file content, fileName, and optional role.
    inputSchema={
        "type": "object",
        "properties": {
            "file": {
                "type": "string",
                "description": "The file content to upload"
            },
            "fileName": {
                "type": "string",
                "description": "The file name"
            },
            "role": {
                "type": "string",
                "description": "The roles of the user"
            }
        },
        "required": ["file", "fileName"],
        "additionalProperties": False
    }
  • mcp_server.py:164-173 (registration)
    Dispatch/execution logic in the MCP server's call_tool handler, validating arguments, calling the rag_tools handler, and returning the result as TextContent.
    elif name == "uploadContentFileAboutOrganization":
        if "file" not in arguments or "fileName" not in arguments:
            raise ValueError("file and fileName parameters are required")
        result = rag_tools.upload_content_file_about_organization(
            arguments["file"],
            arguments["fileName"],
            arguments.get("role", "")
        )
        logger.debug(f"Tool {name} executed successfully")
        return [types.TextContent(type="text", text=str(result))]
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden but only states the action without behavioral details. It does not disclose permissions needed, effects on the system (e.g., overwriting), rate limits, or response format. This is inadequate for a mutation 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.

Conciseness4/5

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

The description is a single, efficient sentence with no wasted words. However, it is under-specified rather than concise, as it lacks necessary context for a mutation tool.

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 mutation tool with no annotations and no output schema, the description is incomplete. It does not cover behavioral aspects, usage context, or differences from siblings, leaving significant gaps for an AI agent to understand proper 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 parameters are documented in the schema. The description adds no meaning beyond the schema, such as explaining 'role' usage or file format constraints. Baseline 3 is appropriate as the schema handles parameter documentation.

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

Purpose2/5

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

The description 'Upload content file about the organization' restates the tool name with minimal elaboration, making it tautological. It specifies the verb ('upload') and resource ('content file about the organization') but lacks detail on what this means operationally or how it differs from sibling tools like 'uploadContentUrlAboutOrganization'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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. It does not mention prerequisites, context for file uploads, or distinctions from sibling tools such as 'uploadContentUrlAboutOrganization' (for URLs) or 'listContentNames' (for listing).

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/yogeshkulkarni553/rag-mcp-py'

If you have feedback or need assistance with the MCP directory API, please join our Discord server