Skip to main content
Glama

List catalog connectors

list_catalog_connectors
Read-onlyIdempotent

List the connectors Valet curates — the catalog an organization creates a connector from. Reach for it when list_connectors returned nothing that serves the data a page needs: the organization has no connector for it yet, and this says whether Valet has an entry for the product and what setting it up would take.

Each entry says how its credential arrives. An entry whose credential is a secret names each slot and what it holds, names and descriptions only: create_connector takes no slot or value, and returns a request whose page the person opens to enter each required value the organization does not hold yet. An entry that authorizes in a browser, or connects through Composio, says so — a person completes those in a browser, and no answer here can stand in for that.

Each entry also says whether a website's pages could call it. That is a marker, not a filter: an entry only an agent's container can run is still listed, because "Valet has your product, but no page can call it" is a real answer and reporting it as missing is not. Requires connecting a Valet account.

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

Input Schema

NameRequiredDescriptionDefault
org_nameNoThe Valet organization a connector would be created in. The catalog is the same for every organization; this names the one the answer points the next step at. Omit to use the organization the account joined first.

Output Schema

NameRequiredDescriptionDefault
orgYesName of the Valet organization the call acted in.
connectorsYesThe connectors Valet curates. Empty when the catalog holds none.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedOutput schema / properties / connectors / items / properties / auth / description
      Previous value: -"How the credential arrives: oauth when a person authorizes in a browser, managed when Composio collects it in a browser, secret when it is one or more values the call supplies, none when the connector needs no credential."New value: +"How the credential arrives: oauth when a person authorizes in a browser, managed when Composio collects it in a browser, secret when a person enters one or more values on the request page create_connector returns, none when the connector needs no credential."
    • changedOutput schema / properties / connectors / items / properties / slots / description
      Previous value: -"The secret values the entry asks for. Present only when auth is secret."New value: +"The secrets the entry needs, by name and description only. No tool takes their values: a person enters each required one on the request page create_connector returns. Present only when auth is secret."
    • changedOutput schema / properties / connectors / items / properties / slots / items / properties / name / description
      Previous value: -"The slot's name, as create_connector takes it."New value: +"The slot's name, which the request page shows the person beside the value they enter."
  2. Changed12 schema fields changed
    • addedOutput schema / properties / connectors / description
      Added value: +"The connectors Valet curates. Empty when the catalog holds none."
    • addedOutput schema / properties / connectors / items / properties / auth / description
      Added value: +"How the credential arrives: oauth when a person authorizes in a browser, managed when Composio collects it in a browser, secret when it is one or more values the call supplies, none when the connector needs no credential."
    • addedOutput schema / properties / connectors / items / properties / description / description
      Added value: +"What the connector reaches. Absent when the entry has none."
    • addedOutput schema / properties / connectors / items / properties / name / description
      Added value: +"The entry's name, which create_connector takes."
    • addedOutput schema / properties / connectors / items / properties / site_compatible / description
      Added value: +"True when a website's pages could call the connector once it is created and attached. False means only an agent's container can run it."
    • addedOutput schema / properties / connectors / items / properties / slots / description
      Added value: +"The secret values the entry asks for. Present only when auth is secret."
    • addedOutput schema / properties / connectors / items / properties / slots / items / properties / description / description
      Added value: +"What the value is. Absent when the entry gives none."
    • addedOutput schema / properties / connectors / items / properties / slots / items / properties / name / description
      Added value: +"The slot's name, as create_connector takes it."
    • addedOutput schema / properties / connectors / items / properties / slots / items / properties / optional / description
      Added value: +"True when the slot may be left out. Absent when it is required."
    • addedOutput schema / properties / connectors / items / properties / transport / description
      Added value: +"How Valet talks to the connector. Absent for a command connector, which has none."
    • addedOutput schema / properties / connectors / items / properties / type / description
      Added value: +"How Valet runs the connector, such as an MCP server or a command."
    • addedOutput schema / properties / org / description
      Added value: +"Name of the Valet organization the call acted in."
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "connectors": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "auth": {
      +            "type": "string"
      +          },
      +          "description": {
      +            "type": "string"
      +          },
      +          "name": {
      +            "type": "string"
      +          },
      +          "site_compatible": {
      +            "type": "boolean"
      +          },
      +          "slots": {
      +            "items": {
      +              "additionalProperties": false,
      +              "properties": {
      +                "description": {
      +                  "type": "string"
      +                },
      +                "name": {
      +                  "type": "string"
      +                },
      +                "optional": {
      +                  "type": "boolean"
      +                }
      +              },
      +              "required": [
      +                "name"
      +              ],
      +              "type": "object"
      +            },
      +            "type": [
      +              "null",
      +              "array"
      +            ]
      +          },
      +          "transport": {
      +            "type": "string"
      +          },
      +          "type": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "name",
      +          "type",
      +          "auth",
      +          "site_compatible"
      +        ],
      +        "type": "object"
      +      },
      +      "type": [
      +        "null",
      +        "array"
      +      ]
      +    },
      +    "org": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "org",
      +    "connectors"
      +  ],
      +  "type": "object"
      +}
  4. Added
  5. Removed
  6. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint/idempotent/non-destructive), but the description adds genuinely useful non-annotation context: an account connection prerequisite, that entries reveal credential arrival mode (secret slots vs browser vs Composio), that secret slots expose names and descriptions only and never values, and that page-callability is a marker rather than a filter so a container-only entry is still reported. The last point is valuable because it stops the agent from treating an unpage-callable entry as absent. It loses a point for prose that is dense enough to be easy to misread.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The lead sentence is well front-loaded, but the body balloons into long clause-chained sentences, and much of the return-content explanation duplicates what the output schema already provides. Phrases like 'create_connector takes no slot or value, and returns a request whose page the person opens' take several passes to parse, which is avoidable in a tool-selection description.

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 an output schema present, the description does not need to describe entry fields, yet it still conveys the behavioral constraints an agent needs: account prerequisite, credential-mode variety, values never returned, and the marker-not-filter rule. Nothing essential is missing, though the credential-authorization explanation could be stated more crisply.

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 org_name parameter is fully documented there, including the omit-to-use-default behavior, so the schema carries the semantics. The description never mentions org_name and adds nothing about how the parameter shapes the answer beyond the schema's own claim that the catalog is identical across organizations. Baseline 3 applies when structured fields do the work.

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?

Opens with a specific verb+resource pair ('List the connectors Valet curates') and immediately defines the scope that matters: this is the catalog an organization creates a connector from, not the organization's installed connectors. That framing alone separates it from the sibling list_connectors without opening either schema.

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 trigger and an explicit alternative: come here when list_connectors returned nothing that serves the page's data need. It also explains the downstream hand-off semantics (create_connector takes no slot or value; a person completes secrets in a browser), which prevents the agent from trying to satisfy credentials through this tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources