Skip to main content
Glama
Sign In

Slack MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

Slack Data Query

query_data
Read-only

Query Slack data (Step 3 (FINAL) of workflow).

REQUIRED: Complete these steps first using query_contexts:

  1. request='accounts' - Get workspace_id, brand_id AND available_actions

  2. request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] - Get detailed body structure for specific action(s) using actions from available_actions

IMPORTANT: Always call step 2 to see the exact body structure before querying.

Rely on info from steps 1-2 to construct the query body. Follow the schema exactly.

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": {
      "body": "<body>"
    },
    "name": "query_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already state readOnlyHint=true and openWorldHint=true, and the description is consistent by describing a query operation. It adds useful behavioral context about the required workflow order and the need to construct the body from prior query_contexts calls. It does not cover rate limits or error behavior, but with annotations present the description provides solid additional context.

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 front-loaded with the tool's role and then presents the required steps in a clear numbered list. It is appropriately sized for a workflow-gated tool, though the placeholder 'xxxxxx' entries and repeated emphasis on step 2 add minor verbosity.

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?

Given that an output schema exists, the description need not explain return values. It gives enough workflow context to call the tool correctly: complete the two query_contexts steps first, then build the body from those results. The remaining gap is that the actual body fields are not described here, but the description explicitly routes the agent to where that structure is provided.

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 0%, and the single parameter is a free-form body object with additionalProperties=true, so the schema itself gives almost no semantic detail. The description partially compensates by directing the agent to query_contexts actions_details for the exact body structure, but it does not describe any body fields directly, leaving the parameter semantics dependent on an external workflow step.

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 says 'Query Slack data' and identifies this as 'Step 3 (FINAL) of workflow,' which gives a basic verb and resource. However, it does not specify what kind of Slack data is queried or how this differs from sibling tools such as execute_action, so the purpose remains broad rather than sharply differentiated.

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 gives explicit prerequisites: call query_contexts with request='accounts' and then request='actions_details' before using this tool. It also stresses 'Always call step 2' and to rely on those outputs, which is strong contextual guidance. It does not name alternatives or when-not-to-use cases, keeping it below a 5.

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

All Slack MCP by InsightfulPipe toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources