Skip to main content
Glama

Valet

by io.github.valetdotdev

List connectors a website can hold

list_attachable_connectors
Read-onlyIdempotent

List the organization connectors a website can hold — the discovery step before attach_site_connector.

Only connectors a page can actually call appear: HTTP MCP servers reached over the sse or streamable-http transport. Command connectors and stdio MCP servers are excluded by definition — they run inside an agent's container and no page can reach them — so a connector the organization has that is not listed here cannot back a site.

Pass site to mark which connectors that site already holds; attached connectors stay listed because attaching is idempotent. Tool schemas are not included — attach the connector, then list_site_connectors reports its live tools and their schemas, which is the moment to write the page's calls. Requires connecting a Valet account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteNoA site to mark already-attached connectors against. Omit for the plain organization-wide list.
org_nameNoThe Valet organization whose connectors to list. Omit to use the organization the account joined first.

TDQS

A4.6/5.0
Behavior5/5

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

Despite annotations already marking read-only/idempotent, the description adds significant behavioral context: it explains which connector types are included (HTTP over sse/streamable-http), why excluded ones cannot back a site, that attached connectors remain listed due to idempotency, that schemas are omitted, and that a Valet account connection is required. No contradiction.

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 front-loaded with the core purpose and uses several sentences to explain exclusions, idempotency, and prerequisites. Each sentence adds value, but the length is slightly higher than the minimum needed. Still well-structured and not wasteful.

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 tool with two optional params and no output schema, the description covers necessary context: supported transports, exclusions, idempotent behavior, lack of schemas, and account prerequisite. It is complete for an agent to decide when and how to invoke it.

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?

Input schema covers both parameters (site, org_name) with clear descriptions, achieving 100% schema coverage. The description only briefly reiterates that 'site' marks already-attached connectors, adding little beyond the schema. Baseline 3 is appropriate.

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 clearly states the tool lists organization connectors a website can hold, framed as 'the discovery step before attach_site_connector.' This specific verb+resource pair distinguishes it from sibling tools like list_site_connectors, which reports already-attached connectors with schemas.

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 explicitly says when to use this tool (before attaching a connector) and provides exclusions (command/stdio connectors) plus a pointer to list_site_connectors for post-attachment schema details. This gives clear when-to-use and alternative guidance.

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.3/5.0
Disambiguation5/5

Every tool pairs a distinct resource with one action: site, connector, catalog, design system, access, and sharing are separate concerns. The four list_* tools are clearly differentiated by object (sites, site connectors, attachable connectors, catalog connectors), and attach/detach, publish/rename/delete, and set/share are unambiguous.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern with no stray camelCase or inconsistent verb styles. The naming is predictable: list_X for discovery, get_X for single reads, create_/delete_/rename_/attach_/etach_ for lifecycle actions, and set_/ share_/ call_ for specific operations.

Tool Count4/5

At 16 tools the server is slightly over the ideal 3-15 range, but each tool addresses a distinct part of the site-publishing and connector-attachment workflow. None feel redundant, and the set remains navigable despite being a bit dense.

Completeness4/5

The site lifecycle is essentially complete: publish, read, list, rename, set access, share, and delete, with updates supported through republishing. The connector lifecycle covers discovery, creation, attachment, listing, calling, and detach, but there is no connector update/delete or share-revocation tool, which are minor gaps agents can work around.

Resources