Skip to main content
Glama
yogeshkulkarni553

Content Server

uploadContentUrlAboutOrganization

Upload URLs containing organizational information to store content about companies or institutions. Specify user roles for access control.

Instructions

Upload content url about the organization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL to upload
roleNoThe roles of the user

Implementation Reference

  • The core handler function that performs the URL upload by delegating to rag_service.upload_url and returns a success message.
    def upload_content_url_about_organization(self, url: str, role: str = "") -> list[str]:
        """
        Upload content url about the organization.
    
        Args:
            url: The URL to upload
            role: The roles of the user
    
        Returns:
            Success message
        """
        self.rag_service.upload_url(url, role, self.user_id_from_environment)
        return ["URL uploaded successfully"]
  • The MCP tool schema definition including input schema, properties, required fields, and description.
    types.Tool(
        name="uploadContentUrlAboutOrganization",
        description="Upload content url about the organization",
        inputSchema={
            "type": "object",
            "properties": {
                "url": {
                    "type": "string",
                    "description": "The URL to upload"
                },
                "role": {
                    "type": "string",
                    "description": "The roles of the user"
                }
            },
            "required": ["url"],
            "additionalProperties": False
        }
    )
  • mcp_server.py:175-183 (registration)
    The dispatch logic in the MCP call_tool handler that validates arguments and invokes the tool handler.
    elif name == "uploadContentUrlAboutOrganization":
        if "url" not in arguments:
            raise ValueError("url parameter is required")
        result = rag_tools.upload_content_url_about_organization(
            arguments["url"],
            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 doesn't disclose permissions needed, rate limits, whether it's idempotent, or what happens on success/failure. 'Upload' suggests mutation, but no safety or side-effect information is provided.

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

Conciseness5/5

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

The description is a single, efficient sentence with no wasted words. It's front-loaded and appropriately sized for the tool's apparent complexity, making it easy to parse quickly.

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 lacks details on what 'content' means, how the upload integrates with the organization, or what the tool returns. Given the context, more information is needed for effective use.

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 'url' and 'role' are documented in the schema. The description adds no meaning beyond the schema, as it doesn't explain parameter interactions or provide examples. Baseline 3 is appropriate since the schema handles documentation.

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 'Upload content url about the organization' states the action (upload) and resource (content url about organization), but it's vague about what 'content' entails and doesn't distinguish from sibling 'uploadContentFileAboutOrganization'. It provides a basic purpose but lacks specificity.

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 on when to use this tool versus alternatives like 'uploadContentFileAboutOrganization' or 'searchOrganizationContents'. The description implies uploading from a URL, but it doesn't specify contexts, 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/yogeshkulkarni553/rag-mcp-py'

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