Skip to main content
Glama

Valet

by io.github.valetdotdev

Set website access

set_site_access
Idempotent

Set who can reach a website: public serves it to anyone who has the link, private serves it only to members of the organization that owns it, and password serves it to anyone who enters a shared visitor password. Requires connecting a Valet account.

Password mode takes the password as the password argument. It is a shared visitor password the owner hands to whoever should see the site, not a Valet credential, and it is at most 72 bytes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYesRequired. The access mode. public serves the site to anyone who has the link. private serves it only to members of the organization that owns it. password serves it to anyone who enters the shared visitor password.
nameYesRequired. The site's name.
org_nameNoThe Valet organization the site belongs to. Omit to use the organization the account joined first.
passwordNoThe shared visitor password. Required for password mode and rejected for the others. Anyone who enters it can open the site, so a site's owner passes it to whoever should see the page. At most 72 bytes.

Schema Changelog

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

  1. Changed2 schema fields changed
    • changedInput schema / properties / mode / description
      Previous value: -"public serves the site to anyone who has the link. private serves it only to members of the organization that owns it. password serves it to anyone who enters the shared visitor password."New value: +"Required. The access mode. public serves the site to anyone who has the link. private serves it only to members of the organization that owns it. password serves it to anyone who enters the shared visitor password."
    • changedInput schema / properties / name / description
      Previous value: -"The site's name."New value: +"Required. The site's name."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already communicate idempotency, non-read-only, and non-destructive behavior. The description adds meaningful context beyond that: a Valet-account prerequisite, the clarification that the password is a shared visitor credential rather than a Valet credential, and the 72-byte limit. This does not contradict any annotation.

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 mode definitions, and the password clarification is compact. It is slightly redundant with the already-detailed schema descriptions, but it contains no fluff and reads clearly.

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?

With full schema coverage, useful annotations, and no output schema, the description plus schema gives the agent everything needed to invoke the tool correctly: prerequisite, mode effects, password constraint, and required/optional fields. There is no critical gap for calling this tool.

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?

The input schema has 100% parameter coverage and already explains mode semantics and password constraints. The description largely restates the schema's mode and password content rather than adding new parameter-level meaning, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ('Set who can reach a website') and clearly enumerates the three access modes with their effects. It unambiguously states what the tool does, but it does not explicitly distinguish itself from sibling tools such as share_site or publish_site, which prevents a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides a concrete prerequisite ('Requires connecting a Valet account') and explains the scenarios for each mode, so the agent knows when the tool is applicable. However, it does not say when to prefer this tool over alternatives like share_site or publis_site, leaving some routing to inference.

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