Skip to main content
Glama

Create a connector from the catalog

create_connector
Idempotent

Create an organization connector from a Valet catalog entry. It is the step after list_catalog_connectors found the entry for the product the user named; attach_connector then lets a website's pages call it.

An entry that needs no key, or whose keys the organization already holds as secrets, is created at once. An entry that needs a key from a person is not created here. Give reason, saying plainly why it is needed. The answer carries a request whose url the person opens, signed in to Valet, to enter each key; the connector is created when they complete it, and its name is in the answer now. Give the person the url, then follow the request with get_request. Never ask the person to type a key into this conversation. Optional keys are not asked for; the person can add them on the dashboard's Integrations page.

An entry that authorizes in a browser, OAuth or a Composio toolkit, makes a request the same way: the person opens its url, signs in to the provider from there, and the connector is created under the name in the answer. An entry the organization already has is refused, naming list_connectors; no second connector is made. Returns the connector's name, the catalog entry it came from, the slots filled from secrets the organization already held, whether a website can hold it, and the request when a person must enter keys or sign in. Requires connecting a Valet account.

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": {
      "entry": "<entry>"
    },
    "name": "create_connector"
  }
}

Input Schema

NameRequiredDescriptionDefault
entryYesWhich catalog connector to add to the organization, named as list_catalog_connectors lists it.
reasonNoShown to the person on the request page to explain why the values are needed, so they can decide whether to enter them, such as: The agent reads Linear tickets and needs your Linear sign-in.
org_nameNoThe Valet organization to create the connector in. Omit to use the organization the account joined first.

Output Schema

NameRequiredDescriptionDefault
orgYesName of the Valet organization the call acted in.
entryYesThe catalog entry the connector came from, in the catalog's own spelling.
requestNoThe request a person completes in the dashboard to enter a value that must not pass through this conversation. Absent when nothing needs a person.
secretsNoNames of the secret slots filled from secrets the organization already held. Names only, never values. Absent when none were filled.
connectorYesThe connector's name, which attach_connector takes. While request is set the connector does not exist yet; it takes this name when the person completes the request.
site_compatibleYesTrue when a website can hold this connector once it is created: an HTTP MCP server. False means only agents can attach it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / entry / description
      Previous value: -"The catalog entry's name, spelled exactly as list_catalog_connectors reports it."New value: +"Which catalog connector to add to the organization, named as list_catalog_connectors lists it."
    • changedInput schema / properties / reason / description
      Previous value: -"Why the request is made, in words the person reads on the request page before entering anything, so they know what the values are for, such as: The agent reads Linear tickets and needs your Linear sign-in."New value: +"Shown to the person on the request page to explain why the values are needed, so they can decide whether to enter them, such as: The agent reads Linear tickets and needs your Linear sign-in."
  2. Changed1 schema field changed
    • changedInput schema / properties / reason / description
      Previous value: -"Why the request is made, in the words the person reads on the request page, such as: The agent reads Linear tickets and needs your Linear sign-in."New value: +"Why the request is made, in words the person reads on the request page before entering anything, so they know what the values are for, such as: The agent reads Linear tickets and needs your Linear sign-in."
  3. Changed1 schema field changed
    • changedInput schema / properties / reason / description
      Previous value: -"Why the request is made, in the words the person reads on the request page, such as: The agent reads Linear tickets and needs your Linear sign-in. Needed when the entry requires a key or a sign-in from a person."New value: +"Why the request is made, in the words the person reads on the request page, such as: The agent reads Linear tickets and needs your Linear sign-in."
  4. Changed1 schema field changed
    • changedInput schema / properties / reason / description
      Previous value: -"Needed when the entry requires a key or a sign-in from a person. Why the request is made, in the words the person reads on the request page, such as: The agent reads Linear tickets and needs your Linear sign-in."New value: +"Why the request is made, in the words the person reads on the request page, such as: The agent reads Linear tickets and needs your Linear sign-in. Needed when the entry requires a key or a sign-in from a person."
  5. Changed1 schema field changed
    • changedInput schema / properties / reason / description
      Previous value: -"Needed when the entry requires a key or a sign-in from a person. Why the value is needed, in the words the person reads on the request page, such as: The app charges cards and needs your Stripe key."New value: +"Needed when the entry requires a key or a sign-in from a person. Why the request is made, in the words the person reads on the request page, such as: The agent reads Linear tickets and needs your Linear sign-in."
  6. Changed1 schema field changed
    • changedInput schema / properties / reason / description
      Previous value: -"Needed when the entry requires a key or a sign-in from a person. One plain sentence, shown to the person on the request page, saying why the value is needed, such as: The app charges cards and needs your Stripe key."New value: +"Needed when the entry requires a key or a sign-in from a person. Why the value is needed, in the words the person reads on the request page, such as: The app charges cards and needs your Stripe key."
  7. Changed13 schema fields changed
    • changedInput schema / properties / entry / description
      Previous value: -"Required. The catalog entry's name, spelled exactly as list_catalog_connectors reports it."New value: +"The catalog entry's name, spelled exactly as list_catalog_connectors reports it."
    • changedInput schema / properties / reason / description
      Previous value: -"Required when the entry needs a key or a sign-in from a person. One plain sentence, shown to the person on the request page, saying why the value is needed, such as: The app charges cards and needs your Stripe key. At most 280 characters."New value: +"Needed when the entry requires a key or a sign-in from a person. One plain sentence, shown to the person on the request page, saying why the value is needed, such as: The app charges cards and needs your Stripe key."
    • addedOutput schema / properties / connector / description
      Added value: +"The connector's name, which attach_connector takes. While request is set the connector does not exist yet; it takes this name when the person completes the request."
    • addedOutput schema / properties / entry / description
      Added value: +"The catalog entry the connector came from, in the catalog's own spelling."
    • addedOutput schema / properties / org / description
      Added value: +"Name of the Valet organization the call acted in."
    • addedOutput schema / properties / request / description
      Added value: +"The request a person completes in the dashboard to enter a value that must not pass through this conversation. Absent when nothing needs a person."
    • addedOutput schema / properties / request / properties / expires_at / description
      Added value: +"When the request expires unanswered, as an RFC 3339 UTC time."
    • addedOutput schema / properties / request / properties / fields / description
      Added value: +"Names of what the person enters, never values."
    • addedOutput schema / properties / request / properties / id / description
      Added value: +"Id of the request. Pass it to get_request to follow the request."
    • addedOutput schema / properties / request / properties / next_step / description
      Added value: +"What to do next: give the person the url, then follow the request with get_request."
    • addedOutput schema / properties / request / properties / url / description
      Added value: +"Dashboard page to give the person. They open it signed in to Valet to complete the request. It holds no credential."
    • addedOutput schema / properties / secrets / description
      Added value: +"Names of the secret slots filled from secrets the organization already held. Names only, never values. Absent when none were filled."
    • addedOutput schema / properties / site_compatible / description
      Added value: +"True when a website can hold this connector once it is created: an HTTP MCP server. False means only agents can attach it."
  8. Changed3 schema fields changed
    • addedInput schema / properties / reason
      Added value: +{
      +  "description": "Required when the entry needs a key or a sign-in from a person. One plain sentence, shown to the person on the request page, saying why the value is needed, such as: The app charges cards and needs your Stripe key. At most 280 characters.",
      +  "maxLength": 280,
      +  "type": "string"
      +}
    • removedInput schema / properties / secrets
      Removed value: -{
      -  "additionalProperties": {
      -    "type": "string"
      -  },
      -  "description": "The entry's secret slots, as slot name to value. Valet stores each as an organization secret. A value passed here travels through this conversation; leave it out and point the user at the dashboard's Integrations page when they would rather it did not. A slot the organization already holds needs no value.",
      -  "type": "object"
      -}
    • addedOutput schema / properties / request
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "expires_at": {
      +      "type": "string"
      +    },
      +    "fields": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": [
      +        "null",
      +        "array"
      +      ]
      +    },
      +    "id": {
      +      "type": "string"
      +    },
      +    "next_step": {
      +      "type": "string"
      +    },
      +    "url": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "id",
      +    "url",
      +    "expires_at",
      +    "fields",
      +    "next_step"
      +  ],
      +  "type": [
      +    "null",
      +    "object"
      +  ]
      +}
  9. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "connector": {
      +      "type": "string"
      +    },
      +    "entry": {
      +      "type": "string"
      +    },
      +    "org": {
      +      "type": "string"
      +    },
      +    "secrets": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": [
      +        "null",
      +        "array"
      +      ]
      +    },
      +    "site_compatible": {
      +      "type": "boolean"
      +    }
      +  },
      +  "required": [
      +    "org",
      +    "entry",
      +    "connector",
      +    "site_compatible"
      +  ],
      +  "type": "object"
      +}
  10. Changed1 schema field changed
    • changedInput schema / properties / entry / description
      Previous value: -"Required. The catalog entry's name, spelled exactly as list_connector_catalog reports it."New value: +"Required. The catalog entry's name, spelled exactly as list_catalog_connectors reports it."
  11. Changed1 schema field changed
    • changedInput schema / properties / entry / description
      Previous value: -"Required. The catalog entry's name, spelled exactly as list_catalog_connectors reports it."New value: +"Required. The catalog entry's name, spelled exactly as list_connector_catalog reports it."
  12. Changed1 schema field changed
    • changedInput schema / properties / entry / description
      Previous value: -"The catalog entry's name, spelled exactly as list_catalog_connectors reports it."New value: +"Required. The catalog entry's name, spelled exactly as list_catalog_connectors reports it."
  13. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only supply the safety profile (readOnly=false, idempotent=true, openWorld=false, destructive=false); the description adds the real behavioral texture: entries with no key succeed immediately, person-supplied keys and OAuth/Composio flows produce a signed request URL instead of a connector, the connector name is returned immediately anyway, duplicates are refused, and the agent is told never to collect keys in conversation. That is substantive disclosure beyond the structured fields.

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 and sequence, then branches by entry type (no key / person key / OAuth / duplicate) in a readable order. Slightly overlong: the closing enumeration of return fields duplicates the output schema, and phrases like "in the answer now" and "under the name in the answer" repeat the same point.

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?

For a multi-branch creation tool with an asynchronous person-facing handoff, the description covers every path an agent must handle, including the refusal case and the required follow-up with get_request. The output schema makes the return-value sentence redundant, 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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: 'reason' is framed as the text a person reads before deciding to enter keys, and 'entry' is tied to the exact naming used by list_catalog_connectors. It also clarifies that optional keys are never solicited, which shapes how reason should be written.

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 ("Create an organization connector from a Valet catalog entry") and positions it in the sequence relative to two named siblings: it follows list_catalog_connectors and precedes attach_connector. An agent can distinguish it from create_channel/create_service and from list_connectors without opening any 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?

Explicit routing: use it after list_catalog_connectors identified the entry, use attach_connector to make a website's pages call it, and the check for an existing connector is redirected to list_connectors. It also states the boundary case where the tool does not finish creation by itself and hands off to get_request.

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