Skip to main content
Glama
Sign In

Valet

by io.github.valetdotdev
OverviewDiscussionsAdmin

Revoke website, app, agent, or skill shares

unshare_service
DestructiveIdempotent

Revoke people's shares of a website, an app, an agent, or a skill, by email. Each address's link stops working at once, and revoking is permanent: sharing again with the same address mails a new link. This cannot be undone, so confirm the addresses with the user first. An address with no share is reported, not refused. Sharing does not change who else can reach it. Requires connecting a Valet account.

Input Schema

NameRequiredDescriptionDefault
kindNoThe kind you mean. Omit to act on whatever the name holds; give it to have a name holding another kind refused.
nameYesRequired. The website's, app's, agent's, or skill's name.
emailsYesRequired. The email addresses whose shares to revoke, at most 10 at a time.
org_nameNoThe Valet organization the website, app, agent, or skill belongs to. Omit to use the organization the account joined first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / kind / enum
      Previous value: -[
-  "site",
-  "app",
-  "skill"
-]New value: +[
+  "site",
+  "app",
+  "agent",
+  "skill"
+]
    • changedInput schema / properties / name / description
      Previous value: -"Required. The website's, app's, or skill's name."New value: +"Required. The website's, app's, agent's, or skill's name."
    • changedInput schema / properties / org_name / description
      Previous value: -"The Valet organization the website, app, or skill belongs to. Omit to use the organization the account joined first."New value: +"The Valet organization the website, app, agent, or skill belongs to. Omit to use the organization the account joined first."
  2. Changed2 schema fields changed
    • changedInput schema / properties / name / description
      Previous value: -"Required. The website's or skill's name."New value: +"Required. The website's, app's, or skill's name."
    • changedInput schema / properties / org_name / description
      Previous value: -"The Valet organization the website or skill belongs to. Omit to use the organization the account joined first."New value: +"The Valet organization the website, app, or skill belongs to. Omit to use the organization the account joined first."
  3. Changed3 schema fields changed
    • changedInput schema / properties / kind / enum
      Previous value: -[
-  "site",
-  "app"
-]New value: +[
+  "site",
+  "app",
+  "skill"
+]
    • changedInput schema / properties / name / description
      Previous value: -"Required. The website's name."New value: +"Required. The website's or skill's name."
    • changedInput schema / properties / org_name / description
      Previous value: -"The Valet organization the website belongs to. Omit to use the organization the account joined first."New value: +"The Valet organization the website or skill belongs to. Omit to use the organization the account joined first."
  4. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag destructive and idempotent, but the description adds substantial context: the link stops working at once, revocation is permanent and cannot be undone, re-sharing mails a fresh link, unknown addresses are reported rather than refused, and a Valet account connection is required. These are exactly the details an agent needs before a destructive call.

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 irreversible effect and the confirmation requirement are front-loaded where they matter most. Slight redundancy between 'revoking is permanent' and 'This cannot be undone' costs a little, but overall every sentence carries weight.

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 no output schema, the description covers the return behavior an agent would otherwise lack (non-existent addresses are reported, not refused) and notes the account prerequisite. Nothing needed to call it safely is missing.

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?

Schema coverage is 100%, so kind, name, emails, and org_name are fully documented already, including the 10-address cap and enum values. The description mentions only that revocation is per-email address and adds no format or constraint detail beyond the schema, so the baseline 3 applies.

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 ('Revoke') and resource ('shares of a website, an app, an agent, or a skill') plus the scoping key ('by email'). This cleanly distinguishes it from the sibling share_service, which does the opposite.

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?

Gives a clear precondition ('confirm the addresses with the user first') and the immediate counterpart is implied by naming the re-share behavior. It doesn't explicitly name share_service as the alternative, so routing is inferred rather than instructed.

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
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources