Skip to main content
Glama
RPasquale

lightbulb-mcp

by RPasquale
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

salesforce_bulk_ingest_close

Destructive

Close a Salesforce bulk data ingest by submitting a free-text objective and optional structured inputs. Invokes the domain agent action to finalize the ingestion operation.

Instructions

Run the salesforce domain agent action bulk_ingest_close.

Routes through the platform's domain-agent dispatcher under your JWT, tenant, and company scope.

Args: message: Free-text objective for the action. inputs: Optional JSON string of structured inputs for the action.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputsNo{}
messageNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.1
    • removedInput schema / properties / arguments
      Removed value: -{
-  "default": "{}",
-  "title": "Arguments",
-  "type": "string"
-}
    • addedInput schema / properties / inputs
      Added value: +{
+  "default": "{}",
+  "title": "Inputs",
+  "type": "string"
+}
    • addedInput schema / properties / message
      Added value: +{
+  "default": "",
+  "title": "Message",
+  "type": "string"
+}
  2. First observedv0.1.0

TDQS

C2.2/5.0
Behavior2/5

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

The annotations indicate destructiveHint: true, but the description does not elaborate on any side effects or behaviors. It only mentions routing through a dispatcher and scoping. No details on what happens when the action is invoked, whether it is synchronous, or what changes it makes. The description adds minimal behavioral context beyond the annotations.

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 concise and well-structured. It has three clear segments: the action statement, the routing context, and the args list. It is not overly verbose and does not include irrelevant information.

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?

The description is incomplete for an agent to use it correctly. It lacks an explanation of the action's purpose, expected behavior, and what it returns. The output schema is not shown in the description. The tool appears to be a variant of connector_salesforce_bulk_ingest_close, but the difference is not explained. Thus, an agent would struggle to decide when to use this tool.

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 description provides brief explanations for both parameters: 'Free-text objective for the action' and 'Optional JSON string of structured inputs for the action.' This gives some meaning that the schema lacks. However, these are generic and do not specify what kind of objective or inputs are expected for this specific action. Still, it covers both parameters, so it is moderately helpful.

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 states the verb 'Run' and identifies the resource as 'the salesforce domain agent action bulk_ingest_close,' but it does not explain what bulk_ingest_close actually does. The additional context about routing and scope does not clarify the purpose. Without prior knowledge of Salesforce bulk ingest terminology, an agent cannot determine what this tool accomplishes.

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 given on when to use this tool versus the connector_salesforce_bulk_ingest_close or other salesforce bulk tools. The description only mentions the mechanism (dispatcher) and not the conditions or scenarios for using it. There is no mention of prerequisites, alternatives, or situations.

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