Skip to main content
Glama
Sign In

Spaces by Peakflo

by ai.peakflo
OverviewDiscussionsAdmin

integrations_list

Read-only

List all active integrations available in your workspace.

Returns integration information including:

  • id: Integration ID (use this for other integration tools)

  • name: Human-readable name

  • type: Integration type (e.g., notion-mcp, slack, github, mongodb, etc.)

  • description: Integration description

  • isActive: Whether the integration is active

  • healthStatus: Current health status

  • hasTools: Whether this integration exposes tools via integration_mcp_tools_list

All integrations with hasTools=true can be used with integration_mcp_tools_list and integration_mcp_tool_call tools.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "integrations_list"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint=false, so safety is covered. The description still adds real context beyond them: only active integrations are returned, and the hasTools flag governs which entries are callable through the MCP tool siblings.

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 purpose is front-loaded in one sentence, followed by a compact field glossary that earns its place because no output schema exists. The bullet list is slightly long but each entry maps to a returned field rather than padding.

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?

With no output schema, the field-by-field return description is exactly what an agent needs to interpret results, and the hasTools routing note closes the loop to the sibling tools. Minor gaps remain, such as ordering and whether the list can be empty, but nothing essential for a correct call is missing.

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?

The tool takes zero parameters, so there is no parameter meaning to add and the baseline of 4 applies. The description correctly implies no filtering or paging inputs are needed, consistent with the empty object schema.

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 first sentence states a specific verb and resource with explicit scope: 'List all active integrations available in your workspace.' It also distinguishes itself from sibling tools by naming integration_mcp_tools_list and integration_mcp_tool_call as the downstream consumers of hasTools=true entries.

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 closing sentence routes the agent: integrations with hasTools=true are the ones usable with integration_mcp_tools_list and integration_mcp_tool_call, and the id field is flagged as the key for other integration tools. It stops short of an explicit 'call this first to discover integrations' instruction or any when-not-to-use condition.

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

All Spaces by Peakflo 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