lightbulb-mcp

Overview Schema Source Related Servers Discussions Admin

notion_query_data_source

Read-onlyIdempotent

Query Notion data through the governed connector by supplying project, connector account, and idempotency references. This read-only operation enforces authorization and supports safe resumable reads.

Instructions

Notion connector operation query_data_source (platform tool notion.query_data_source).

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

B3.3/5.0

Behavior4/5

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

The description meaningfully supplements the annotations by stating that 'effect: Required and must be read; Spring verifies it' and emphasizing that it routes only through a governed connector authority. This clarifies the read-only, authority-bound behavior beyond the readOnlyHint and openWorldHint annotations. No contradiction exists between the description and annotations.

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

Conciseness5/5

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

The description is compact, scannable, and front-loaded with the tool identity and governing constraint, followed by a concise parameter list. Every line adds either context or parameter meaning; there is no filler or repetition beyond the necessary platform reference.

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?

Although an output schema is present, the description never explains what a data source query operation actually involves, what kind of query arguments should be placed in the 'arguments' string, or how this tool relates to nearby Notion tools such as notion_query_data, notion_query_database, and notion_query_view. This leaves significant ambiguity for an agent attempting to construct a correct invocation.

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?

With 0% schema description coverage, the description provides valuable glosses for every parameter: project_id is 'Authenticated Project UUID', connector_account_ref is 'Project-bound connector account alias', and idempotency_key is 'Stable business-action identity'. However, the central 'arguments' parameter is only described as a 'JSON string of arguments for the connector operation', leaving the actual query payload structure unspecified, so it does not fully compensate for the schema gap.

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

Purpose3/5

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

The description identifies the tool as 'Notion connector operation `query_data_source`' and mentions governed authority routing, but it never explicitly says what querying a data source does, what resource it targets, or what it returns. The name itself is semantically suggestive, but the description mostly restates it rather than defining the operation. It also does not differentiate this from siblings like notion_query_data, notion_query_database, and notion_query_view.

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?

The 'Routes only through the exact project/account governed connector authority' line is a routing constraint, not usage guidance. There is no statement of when to use this tool versus alternatives, no exclusions, and no mention of prerequisites for choosing it over sibling Notion query tools. The agent is left to infer when this is the right call.

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

Deploy Server