Skip to main content
Glama

Valet

by io.github.valetdotdev

Share a website by email

share_site
Destructive

Share a website with specific people by email, whether it is private or password-protected — sharing does not change who else can reach it. Each address is mailed a link from Valet that opens the site; the recipient needs no Valet account of their own, only the link, so anyone holding the email can open the site and forwarding it forwards access. Sharing again with an address that already has access re-sends the same link rather than creating a second one. Requires connecting a Valet account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesRequired. The site's name.
emailsYesRequired. The email addresses to share the site with, at most 10 at a time. Sharing again with an address that already has access re-sends the same link rather than creating a second one.
messageNoAn optional note included in the email, shown to the recipient as a quote beside the link. At most 500 characters.
org_nameNoThe Valet organization the site belongs to. Omit to use the organization the account joined first.
access_ttl_secondsNoHow many seconds of access the first open starts, after which the link stops working. Omit, or pass 0, for access that never expires this way. Composes with expires_in_seconds: the unopened deadline governs until the first open replaces it.
expires_in_secondsNoHow many seconds from now the link stops working if nobody has opened it yet. Omit, or pass 0, for a link that never expires this way.

Schema Changelog

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

  1. Changed2 schema fields changed
    • changedInput schema / properties / emails / description
      Previous value: -"The email addresses to share the site with, at most 10 at a time. Sharing again with an address that already has access re-sends the same link rather than creating a second one."New value: +"Required. The email addresses to share the site with, at most 10 at a time. Sharing again with an address that already has access re-sends the same link rather than creating a second one."
    • changedInput schema / properties / name / description
      Previous value: -"The site's name."New value: +"Required. The site's name."
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

The description discloses critical behaviors beyond the annotations: it states sharing does not affect other access, explains that forwarding the email forwards access, and clarifies that re-sharing with the same address re-sends the existing link. It also notes the necessity of a Valet account. These details help the agent understand side effects and security implications, complementing the destructiveHint annotation.

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

Conciseness5/5

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

The description is three sentences, each serving a clear purpose: purpose, security behavior, and idempotency. It is front-loaded with the core action and wastes no words. The tone is direct and informative.

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?

Given 6 parameters, no output schema, and annotations that are complemented by the description, the description covers the tool's behavior comprehensively. It explains the security implications, idempotency, account requirement, and the effect of optional parameters. An agent can correctly decide to invoke this tool and understand the expected behavior.

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?

With 100% schema coverage, the baseline is 3. The description adds context by explaining how parameters interact (e.g., access_ttl_seconds and expires_in_seconds compose, at most 10 emails). It also clarifies that sharing again with an existing address re-sends the link, which relates to the emails parameter. This adds value beyond the schema definitions.

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's purpose: 'Share a website with specific people by email.' It specifies that it works for private or password-protected sites and notes that sharing does not change who else can reach it. This distinguishes it from siblings like 'set_site_access' (which changes access) and 'publish_site', covering a unique action.

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

Usage Guidelines4/5

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

The description implies when to use (to email a link) and mentions the requirement to connect a Valet account. However, it does not explicitly contrast with alternatives like 'set_site_access' for programmatic access or 'publish_site' for making a site public. The context is clear but lacks explicit 'when not to use' 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.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