Skip to main content
Glama
RPasquale

lightbulb-mcp

by RPasquale
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

salesforce_bulk_ingest_results

Destructive

Retrieve Salesforce bulk ingest outcome details by sending a free-text objective and optional structured inputs through the Lightbulb domain-agent dispatcher.

Instructions

Run the salesforce domain agent action bulk_ingest_results.

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.3/5.0
Behavior2/5

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

The description adds only that the call routes through the domain-agent dispatcher under JWT/tenant/company scope. It does not disclose what the action does, what it returns, whether it is long-running, or what destructive side effects it may have—significant given destructiveHint=true and readOnlyHint=false. There is no contradiction with annotations, but the behavioral burden is left mostly unmet.

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

Conciseness3/5

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

The description is short and generally readable, but its first sentence is largely a restatement of the tool name and the routing paragraph adds only marginal value. The Args block is efficient but generic; the overall structure is adequate but not tightly front-loaded with the most decision-relevant 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?

Given the large sibling family of Salesforce bulk-ingest tools and the destructive annotation, a complete description would explain what results are being fetched, when to call this instead of status/close/create, and what side effects to expect. The current description is too generic and leaves an agent without enough context to select and invoke this tool confidently.

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 coverage is 0%, so the description carries the full burden for explaining parameters. It adds minimal semantics by calling message a 'free-text objective' and inputs an 'optional JSON string of structured inputs,' which is more than the schema provides. However, it does not explain what structured inputs are expected for bulk_ingest_results specifically, leaving a clear gap.

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 only says 'Run the salesforce domain agent action `bulk_ingest_results`' plus routing details, which essentially restates the tool name without saying what the action actually does. It does not specify that this retrieves results of a bulk ingest operation, nor does it distinguish itself from sibling tools like salesforce_bulk_ingest_status or salesforce_bulk_query_results.

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 given on when to use this tool versus the many related bulk-ingest siblings. The description mentions routing through a dispatcher, but that is plumbing context, not usage guidance. It neither states conditions for use nor excludes alternatives.

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