FleetQ

Overview Schema Source Related Servers Discussions Admin

Integration Manage Tool

integration_manage

Destructive

Manage third-party integrations: list, connect, disconnect, ping, and execute actions on upstream services via typed capabilities.

Instructions

Third-party service integrations (Airtable, Notion, Linear, Stripe, Slack, GitHub via OAuth2 + driver interface). Each integration declares typed capabilities (action endpoints) discoverable at runtime. execute invokes one capability with params validated against the driver's schema; output is normalized to JSON.

Actions:

list (read) — optional: driver, status filter.
connect (write) — driver, name, credentials (object — driver-specific). Initiates OAuth or stores API keys.
disconnect (DESTRUCTIVE) — integration_id. Revokes tokens and deletes the connection.
ping (read) — integration_id. Health-check the upstream API.
execute (write — side effects on upstream) — integration_id, integration_action (capability name), params (object).
capabilities (read) — integration_id. Available actions + parameter schemas.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>",
      "name": "<name>",
      "integration_id": "<integration_id>",
      "integration_action": "<integration_action>"
    },
    "name": "integration_manage"
  }
}

Input Schema

Name	Required	Description
`action`	Yes	Action to perform: list, connect, disconnect, ping, execute, capabilities
`deadline_ms`	No	Optional: max wall-clock time (ms) the tool may spend. If exceeded during the call, returns a DEADLINE_EXCEEDED error. Minimum 100 ms. Leave unset for no deadline.
`driver`	No	Filter by driver slug (e.g. github, slack, notion)
`include_drivers`	No	Include list of available drivers (default false)
`name`	Yes	Human-readable name for this integration instance
`credentials`	No	Credential key-value pairs, e.g. {"token": "ghp_..."}
`config`	No	Driver-specific config, e.g. {"database_id": "..."} for Notion
`integration_id`	Yes	Integration UUID
`integration_action`	Yes	Driver action key, e.g. post_tweet, create_issue, send_message
`params`	No	Action parameters (driver-specific)

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedMay 7, 2026

addedInput schema / properties / deadline_ms

Added value: +{
+  "description": "Optional: max wall-clock time (ms) the tool may spend. If exceeded during the call, returns a DEADLINE_EXCEEDED error. Minimum 100 ms. Leave unset for no deadline.",
+  "type": "number"
+}

addedInput schema / properties / integration_action

Added value: +{
+  "description": "Driver action key, e.g. post_tweet, create_issue, send_message",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "action",
-  "name",
-  "integration_id"
-]New value: +[
+  "action",
+  "name",
+  "integration_id",
+  "integration_action"
+]

First observedv1.10.0Mar 24, 2026

TDQS

B3.3/5.0

Behavior3/5

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

The description discloses behavioral traits like destructiveness for disconnect and side effects for execute, and the annotation already sets destructiveHint: true. However, it does not cover idempotency, rate limits, or auth requirements beyond mentioning OAuth for connect.

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 well-structured with a header and bullet points, and most sentences are necessary. However, it is somewhat verbose; could be more concise without losing clarity.

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 complexity (10 parameters, no output schema), the description fails to explain return values for most actions (only mentions 'output normalized to JSON' for execute). Error handling and detailed behavior for list, connect, etc., are missing.

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 description coverage is 100%, so the baseline is 3. The description adds examples for credentials and config, but does not significantly enrich parameter understanding beyond the schema.

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

Purpose4/5

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

The description clearly states the tool manages third-party integrations with six specific actions (list, connect, disconnect, ping, execute, capabilities) and describes each action's purpose. However, it does not differentiate from the sibling tool 'integration_execute', which could cause confusion about when to use each.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides some usage hints (e.g., 'optional: driver, status filter' for list, and 'DESTRUCTIVE' for disconnect), but lacks explicit guidance on when to use this tool versus alternatives (e.g., sibling integration_execute). No prerequisites or when-not-to-use scenarios are mentioned.

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