Skip to main content
Glama
SmartBear MCP server

SmartBear MCP server

Official
by SmartBear

SmartBear: List Integrations

smartbear_list_integrations
Read-onlyIdempotent

Lists all supported SmartBear products, shows which are configured for this connection, and reveals the environment variable or HTTP header each unconfigured product needs.

Instructions

Lists every SmartBear product this server supports, whether it is configured for this connection, and for unconfigured products the environment variable or HTTP header each setting needs. Only products allowed by the server's MCP_CLIENTS setting are listed. Products that accept per-request OAuth tokens (BearQ, Reflect, QMetry) always show as configured. Takes no parameters.

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": "smartbear_list_integrations"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.44.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world behavior, and the description adds non-obvious rules the annotations cannot convey: results are filtered by the server's MCP_CLIENTS setting, and OAuth-capable products (BearQ, Reflect, QMetry) always report as configured regardless of state. The one gap is that the exact returned structure is only implied, not described.

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?

Three tight sentences plus a closing contract statement, all front-loaded: what it lists, then the filtering rule, then the special-case exception, then parameters. Nothing is redundant or padded.

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 parameterless, read-only discovery tool with no output schema, the description supplies the essential semantics: the filtering rule, the OAuth exception, and the fact that missing products require a specific env var or header. A brief note on the shape of each returned entry would close the last gap, but nothing needed to call it correctly 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?

With zero parameters and 100% schema coverage, the baseline of 4 applies. The description confirms the no-argument contract explicitly, which removes any doubt about whether filtering or product selection can be requested.

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 opens with a specific verb and resource ("Lists every SmartBear product this server supports") and immediately scopes what is returned: configuration status per product, plus the env var or HTTP header needed for unconfigured ones. An agent can tell exactly what this tool produces without opening the schema.

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 described output (which products are configured and what each unconfigured one needs) makes the use case clear: discover setup state before attempting other operations. There are no sibling tools, so no alternative routing is needed, but the description never states exclusions or preconditions beyond "takes no parameters."

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

Deploy Server

Other Tools