Box MCP Server

box_file_upload_tool

Upload content as a file to Box, specifying file name and destination folder.

Instructions

Upload content as a file to Box.

Args: content (str | bytes): The content to upload. Can be text or binary data. file_name (str): The name to give the file in Box. parent_folder_id (str): The ID of the destination folder. Defaults to root ("0").

Returns: dict[str, Any]: Information about the uploaded file including id and name.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "content": "<content>",
      "file_name": "<file_name>",
      "parent_folder_id": "<parent_folder_id>"
    },
    "name": "box_file_upload_tool"
  }
}

Input Schema

Name	Required	Description	Default
`content`	Yes
`file_name`	Yes
`parent_folder_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.0Oct 21, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic operation. It doesn't disclose behavioral traits like authentication requirements, rate limits, file size limits, overwrite behavior, or error handling. The description is minimal and lacks crucial operational context.

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 well-structured with clear sections (purpose, args, returns) and front-loaded the core functionality. Every sentence adds value, though the 'Args' and 'Returns' sections could be integrated more seamlessly into the narrative flow.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, 0% schema coverage, but an output schema exists, the description is moderately complete. It covers the basic operation and parameters but lacks behavioral context and usage guidance. The output schema handles return values, but the description should address mutation implications and error cases more explicitly.

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?

Schema description coverage is 0%, so the description must compensate. It provides clear semantic explanations for all 3 parameters: content type, file naming, and folder destination with default value. This adds substantial value beyond the bare schema, though it could mention format constraints or ID validation.

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

Purpose5/5

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

The description clearly states the specific action ('Upload content as a file') and resource ('to Box'), distinguishing it from sibling tools like box_file_download_tool or box_file_copy_tool. It uses precise verbs and identifies the exact operation.

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 like box_file_copy_tool or box_folder_create_tool. The description lacks context about prerequisites (e.g., authentication, folder permissions) or when-not-to-use scenarios.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server