lightbulb-mcp

Overview Schema Source Related Servers Discussions Admin

smokeball_list_activities

Read-onlyIdempotent

Retrieve Smokeball activity records for your project by running a read operation through the project-bound connector account.

Instructions

Smokeball connector operation list_activities (platform tool smokeball.list_activities).

Routes only through the exact project/account governed connector authority.

Args: arguments: JSON string of arguments for the connector operation. project_id: Authenticated Project UUID. project_ref: Exact project correlation reference. connector_account_ref: Project-bound connector account alias. idempotency_key: Stable business-action identity. effect: Required and must be read; Spring verifies it. approval_ref: Approved platform task UUID when resuming a write.

Input Schema

TableJSON Schema

Name	Required	Default
`effect`	Yes
`arguments`	No	{}
`project_id`	No
`project_ref`	No
`approval_ref`	No
`idempotency_key`	No
`connector_account_ref`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv0.1.1Sep 7, 2026

addedInput schema / properties / approval_ref

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Approval Ref"
+}

addedInput schema / properties / connector_account_ref

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Connector Account Ref"
+}

addedInput schema / properties / effect

Added value: +{
+  "const": "read",
+  "title": "Effect",
+  "type": "string"
+}

addedInput schema / properties / idempotency_key

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Idempotency Key"
+}

addedInput schema / properties / project_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Project Id"
+}

addedInput schema / properties / project_ref

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Project Ref"
+}

addedInput schema / required
```
Added value: +[
+  "effect"
+]
```

First observedv0.1.0Jun 25, 2026

TDQS

D1.8/5.0

Behavior2/5

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

The description states that the operation 'routes only through the exact project/account governed connector authority,' which is a mild behavioral note about authorization. However, it lacks any additional details about side effects, pagination, rate limits, or what the read operation returns, and it does not add to the annotations beyond that generic routing statement.

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 brief and follows a consistent pattern, but it is repetitive with the input schema and lacks a clear narrative structure. It front-loads the tool name but then dives into a parameter list that mirrors the schema, which adds little value while consuming space.

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

Completeness1/5

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

Given the tool's moderate complexity with seven parameters and a required `arguments` JSON blob, the description is far from complete. It omits essential information such as the meaning of 'activities', the format of the `arguments` payload, any filtering options, and the shape of the response, making it nearly unusable for an agent without prior Smokeball knowledge.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description lists parameters using the same titles as the schema and adds only cryptic notes like 'Required and must be read; Spring verifies it' for `effect`. The crucial `arguments` parameter is described as a 'JSON string of arguments for the connector operation' without any explanation of its internal schema, leaving the agent without sufficient semantic information to construct a valid request.

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 identifies the tool as a Smokeball connector operation named `list_activities`, but it never explains what an 'activity' is in the Smokeball context or what listing them entails. The purpose is only inferable from the name, and the boilerplate text does not distinguish it from sibling list operations like `smokeball_list_matters` or `smokeball_list_contacts`.

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?

The description provides no guidance on when to use this tool, what prerequisites exist, or how it differs from alternatives. It only repeats the schema parameters without any contextual advice, leaving the agent to guess the appropriate use case.

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

Deploy Server