FleetQ

by escapeboy

Overview Schema Source Related Servers Discussions Admin

Hybrid

Integration Execute Tool

integration_execute

Destructive

Execute an action on a connected integration, such as creating a GitHub issue or sending a Slack message.

Instructions

Execute an action on a connected integration, e.g. create_issue on GitHub, send_message on Slack.

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": {
      "integration_id": "<integration_id>",
      "integration_action": "<integration_action>"
    },
    "name": "integration_execute"
  }
}

Input Schema

Name	Required	Description
`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.

AddedMay 7, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already signal destructiveHint:true. The description adds that it executes actions (implying mutation) and gives examples, but does not disclose additional behavioral traits such as required authentication, potential side effects, or rate limits. With annotations covering destructive nature, the description's extra behavioral context is minimal.

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 a single, efficient sentence with examples. Every part earns its place; no wasted words.

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

Completeness4/5

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

For a tool with 3 parameters and no output schema, the description is fairly complete. It explains the action concept and gives examples, but does not cover return values or error behavior, which would be beneficial.

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% with well-described parameters. The description's examples add context for the 'params' object but do not significantly extend beyond the schema. Baseline 3 is appropriate as the description provides no substantial additional meaning.

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

Purpose5/5

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

The description clearly states 'Execute an action on a connected integration' with concrete examples (create_issue on GitHub, send_message on Slack), making the purpose unambiguous and distinguishing it from sibling tools like integration_manage.

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

Usage Guidelines4/5

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

The description provides clear examples of when to use, but does not explicitly mention when not to use or list alternatives. Given the sibling tools are mostly manage tools, the usage context is clear without exclusions.

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