Skip to main content
Glama
Sign In

OTP

by io.github.david-steel
OverviewDiscussionsAdmin

Search the integrations catalog

search_integrations
Read-only

Search the catalog of outside systems that can be connected to OTP (over 1000 apps via Composio). Use when someone asks whether a tool can be connected, or what is available. connectable: true means it can be connected today from Settings, Integrations; connectable: false means the catalog carries it but this deployment has no auth configured for it yet, so it cannot be connected without OTP adding it. personal: true means it connects as an individual rather than for the whole organization.

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": {
      "search": "<search>"
    },
    "name": "search_integrations"
  }
}

Input Schema

NameRequiredDescriptionDefault
searchYesWhat to look for, e.g. 'linear', 'calendar', 'analytics'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, so safety is covered. The description goes further by decoding two result fields — connectable and personal — including the operational consequence ('cannot be connected without OTP adding it'), which is real behavioral context an agent cannot get elsewhere since there is no output schema.

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?

Front-loaded with purpose, then usage trigger, then field semantics — a sensible order. Every sentence carries information, though the connectable/personal explanations are dense and could be tightened slightly.

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 description correctly takes on the burden of explaining returned fields, covering connectable and personal. It does not describe result shape (list vs ranked), pagination, or limits on a 1000+ app catalog, which is a minor remaining gap.

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% and the single 'search' parameter is documented with examples ('linear', 'calendar', 'analytics'). The description adds nothing about matching behavior (substring vs fuzzy, ranking), so the baseline 3 is appropriate.

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?

States a specific verb and resource ('Search the catalog of outside systems that can be connected to OTP') and gives scale context (1000+ apps via Composio). Practically distinguishes itself from the sibling list_connections by focusing on availability rather than existing connections.

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?

Explicitly states the triggering question: 'Use when someone asks whether a tool can be connected, or what is available.' It does not name a sibling alternative (e.g. list_connections for already-connected apps) or state when not to use it, leaving a small inference gap.

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

All OTP 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