Skip to main content
Glama

Connections

by icu.connections
OverviewDiscussionsAdmin

List connected accounts/instances

connections_accounts
Read-only

THE answer to 'is connected?' - every connected account/instance this company has (service, instance, accountId, region), filterable with service and narrowed with match (looking for one plane's instance? pass match - the full list is ~50 rows). Pass an instance as connections_execute's instance to target one. Two kinds: a normal row holds a credential in this vault; a kind:'brokered' row is owned by ANOTHER first-party plane (named in via) that holds the credential - notably every Stripe account linked through Pay, which you reach with Pay endpoints per the row's callWith, NOT with service:'stripe'. Stripe can appear BOTH ways at once and they are different accounts: a brokered row is Pay's Connect link, while a normal stripe row is a secret key this workspace pasted directly and IS called with service:'stripe' as its own instance - so read the row's kind before choosing how to call it. A brokeredUnavailable field means that plane could not be reached, so the list is INCOMPLETE - never read it as 'not connected'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
matchNoOnly accounts whose instance name, account name or account id contains this text (case-insensitive), e.g. 'accounts' for the Accounts plane. Instance names follow `<plane>@connections.icu` for most planes and `Main.Connections` for Main. Combines with `service`.
serviceNoOnly accounts for this service slug (aws, stripe, github, cloudflare, …). Omit for every connected account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / match
      Added value: +{
+  "description": "Only accounts whose instance name, account name or account id contains this text (case-insensitive), e.g. 'accounts' for the Accounts plane. Instance names follow `<plane>@connections.icu` for most planes and `Main.Connections` for Main. Combines with `service`.",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / required
      Added value: +[]
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, but the description adds substantial behavioral detail: two row kinds (normal vs brokered), the `via` and `callWith` fields, and the critical caveat that Stripe can appear both ways with different semantics. It also discloses the incompleteness risk from brokeredUnavailable, far exceeding what annotations convey.

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 long but every sentence earns its place. It is front-loaded with the core purpose and filters, then logically progresses to usage with connections_execute and the nuanced brokered/Stripe handling. The structure guides the agent from high-level to edge cases without redundancy.

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

Completeness5/5

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

Despite lacking an output schema, the description enumerates expected fields (service, instance, accountId, region) and introduces `kind`, `via`, `callWith`, and `brokeredUnavailable`. It also explains how to consume the result for targeting connections_execute, making the tool fully actionable for an agent.

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?

Schema description coverage is 100%, so both parameters are documented. The description adds meaning by explaining how `match` narrows (e.g., instance names follow `<plane>@connections.icu`) and that `service` filters by slug. It also clarifies the combination of filters, going beyond the schema's basic descriptions.

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 states a specific verb (list) and resource (connected accounts/instances) with clear scope: 'every connected account/instance this company has'. It distinguishes itself from siblings by explicitly routing usage to connections_execute and clarifying that Stripe brokered rows are handled via Pay endpoints, not this tool.

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

Usage Guidelines5/5

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

Provides explicit when-to-use ('THE answer to is <service> connected?') and how-to-filter guidance with `service` and `match`. It also gives exclusions: brokered Stripe accounts should use Pay endpoints, and warns that brokeredUnavailable means the list is incomplete, so it must not be read as 'not connected'.

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

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