lightbulb-mcp

Overview Schema Source Related Servers Discussions Admin

microsoft_list_chats

Read-onlyIdempotent

List Microsoft Teams chats from your connected account to review conversations and locate chat IDs for follow-up actions. This read-only operation requires an approved connector reference.

Instructions

Microsoft connector operation list_chats (platform tool microsoft.list_chats).

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

C2/5.0

Behavior3/5

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

Annotations clearly declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, which already convey the non-destructive, read-only, idempotent behavior. The description adds no further transparency about side effects, permissions, or rate limits. It does not contradict the annotations, so a baseline score of 3 is appropriate.

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 short but repetitive, using 'connector operation' and 'project/account governed connector authority' multiple times. It is not well-structured; it reads more like a template than a tailored tool explanation. It could be more concise and informative, but it is not excessively long, so a score of 2 reflects the inefficient use of words.

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?

The description omits essential context: what the returned data looks like, how to specify filters for the list, what the 'arguments' JSON should contain, and any relationship to Microsoft Chat APIs. Given the tool's simple list nature, these gaps are significant and prevent an agent from using it effectively without external knowledge.

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

Parameters1/5

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

Schema description coverage is 0%; the schema provides no descriptions for any parameters. The description merely repeats parameter names with generic phrases (e.g., 'arguments: JSON string of arguments for the connector operation') without explaining their purpose, format, or expected values. It fails to compensate for the missing schema documentation, leaving agents with no meaningful semantics.

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 name 'microsoft_list_chats' implies a chat-listing operation, and the description identifies it as a Microsoft connector operation. However, the description does not explicitly state what the tool does; it focuses on routing authority ('Routes only through the exact project/account governed connector authority') rather than the primary function. This leaves the purpose somewhat implicit and does not clearly distinguish it from many similar sibling list tools.

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 versus alternative list operations or other Microsoft tools. No conditions, context, or examples are given. The only usage-related phrase is about routing, which is not actionable for selecting this tool.

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

Deploy Server