Skip to main content
Glama

Valet

by io.github.valetdotdev

Create a connector from the catalog

create_connector

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_site_connector then lets a website's pages call it.

It creates an entry whose credential is a secret. Pass each slot the entry asks for in secrets, as slot name to value. A slot the organization already holds as a secret needs no value here. If a required slot has neither, nothing is created and the answer names the slots still needed.

A key given here passes through this conversation. That is a real cost and it is the user's call to make: if they hand you the key, use it, and say that they could instead enter it on the dashboard's Integrations page, where it goes straight to Valet. The answer names the slots that were filled and never the values in them.

An entry that authorizes in a browser — OAuth, or a Composio toolkit — is not created here. The answer gives the entry's name and the Integrations page, which creates the connector and runs the authorization in one place. An entry the organization already has is reported as already there; no second connector is made. Requires connecting a Valet account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entryYesRequired. The catalog entry's name, spelled exactly as list_catalog_connectors reports it.
secretsNoThe 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.
org_nameNoThe Valet organization to create the connector in. Omit to use the organization the account joined first.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 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."
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

The description goes well beyond the minimal annotations. It discloses that secrets passed in travel 'through this conversation' with a 'real cost', that the answer only names slots filled and 'never the values', that duplicate entries are reported without creating a second connector, and that missing required slots result in no creation with the missing slots named. This is rich behavioral context.

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?

The description is longer than average but each sentence contributes meaningful operational detail. It is front-loaded with the core purpose and then logically covers workflow, security, and edge cases. While not terse, the density of useful information earns a high score.

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 mutating connector-creation tool with no output schema and minimal annotations, the description covers prerequisites, failure modes, security/privacy implications, duplicate handling, unsupported auth flows, and the relationship to sibling tools. It is sufficiently complete to guide correct invocation.

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?

The input schema already covers 100% of the parameters, so the baseline is 3. The description adds important semantics beyond the schema, such as how to handle secrets ('Pass each slot the entry asks for in secrets, as slot name to value'), that a slot the org already holds needs no value, and that a passed key 'passes through this conversation', which is not in the schema.

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 explicitly states 'Create an organization connector from a Valet catalog entry' and places it in a workflow: 'It is the step after list_catalog_connectors found the entry...; attach_site_connector then lets a website's pages call it.' This clearly distinguishes it from the catalog-listing and site-attaching siblings.

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?

It provides explicit when-to-use context ('the step after list_catalog_connectors') and calls out an important exclusion: 'An entry that authorizes in a browser — OAuth, or a Composio toolkit — is not created here' and directs users to the Integrations page instead. It also notes the prerequisite 'Requires connecting a Valet account.'

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

All Valet toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Every tool targets a distinct resource and action. The three list_* connector tools are clearly separated by scope (catalog vs attachable vs attached), and the site management tools are unambiguous.

Naming Consistency5/5

All tool names follow a uniform verb_noun snake_case pattern. Each name directly states the action and object, with no mixed conventions or vague verbs.

Tool Count4/5

16 tools is slightly above the typical well-scoped range, but the set covers two clear domains—site publishing and connector management—and each tool has a distinct role. The count is justified, if a bit heavy.

Completeness4/5

Site lifecycle is well covered: publish, list, get, rename, delete, access, and share. The connector lifecycle covers create, attach, detach, and call, but lacks delete/update connector operations, which are a minor gap.

Resources