Skip to main content
Glama
Sign In
Files.com MCP Server

Files.com MCP Server

Official
by Files-com
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Update Bundle Notification

Update_Bundle_Notification
Destructive

Modify notification triggers for a bundle to send alerts on user registration or file upload events.

Instructions

Update Share Link Notification

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "Update_Bundle_Notification"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoBundle Notification ID.
notify_on_registrationNoTriggers bundle notification when a registration action occurs for it.
notify_on_uploadNoTriggers bundle notification when a upload action occurs for it.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.65

TDQS

C2.7/5.0
Behavior2/5

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

Annotations indicate destructiveHint=true, so the tool modifies state. The description adds no extra behavioral details beyond 'Update', such as that only specified fields are updated or that id is needed to identify the notification. No contradiction with annotations.

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 extremely brief, consisting of only three words. While concise, it lacks important details and does not effectively communicate the tool's functionality.

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 3 parameters (0 required), an output schema, and annotations, the description is incomplete. It fails to explain that id is likely required for identification, that updates are partial, or what the response looks like.

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?

The input schema has 100% coverage with descriptions for each parameter. The tool description does not add additional meaning about parameters or their relationships, but the schema already documents them adequately.

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 'Update Share Link Notification' includes verb and resource, clearly indicating it updates a notification. However, note that the tool name uses 'Bundle Notification' but description says 'Share Link Notification', which could cause confusion. Still, it is distinct from siblings like Create_Bundle_Notification.

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 Create_Bundle_Notification, Find_Bundle_Notification, or other update tools like Update_Bundle. The description offers no context for usage.

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

Deploy Server

Other Tools