Skip to main content
Glama
Sign In

SetLatch

by com.setlatch
OverviewDiscussionsAdmin

List connected apps

list_connections
Read-onlyIdempotent

The apps a site has connected to SetLatch (Mailchimp, Stripe, Shopify, WooCommerce, HubSpot, Klaviyo, Gmail, Resend, Cloudflare, webhooks), which data map system each serves, and whether it is working. No keys or settings. Use it to see which systems look_up_requester can check; get_data_map lists every system, connected or not.

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": {
      "site": "<site>"
    },
    "name": "list_connections"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesThe site: its slug from list_sites (its id or exact name also work).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety bar is low; the description still adds value by disclosing the negative scope ('No keys or settings') and that health/working status is part of the response. It does not discuss failure modes (e.g. unknown slug) or volume, which keeps it below a 5.

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 the resource, then the distinguishing sibling reference. The long parenthetical app list costs some space but does real work by bounding what 'connected apps' means; the fragmentary grammar of the opening sentence is the only real blemish.

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?

There is no output schema, so the description carries the return-value burden and does it: it says the response lists each app, its mapped system, and whether it works, plus what is excluded. For a single-parameter read tool, an agent has everything needed to call it correctly.

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 coverage is 100% and the single 'site' parameter already documents slug/id/exact-name acceptance, so the description adds no new syntax or format detail. Baseline 3 applies when the schema carries the parameter semantics entirely.

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 the exact resource (apps a site has connected to SetLatch), enumerates the domain of apps, and specifies the per-item fields (data map system, working status). It is immediately distinguishable from get_data_map, which is named as covering every system, connected or not.

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?

Gives an explicit use case ('see which systems look_up_requester can check') and an explicit alternative with the condition that selects it ('get_data_map lists every system, connected or not'). Nothing is left to inference about when to pick this tool.

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

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