Skip to main content
Glama

Set website, app, agent, or skill access

set_service_access
DestructiveIdempotent

Set who can reach a website, app, agent, or skill: public serves it to anyone who has the link, private serves it to members of the organization that owns it after they sign in to Valet, and to anyone a member has shared it with through share_service, who needs no Valet account, and password serves it to anyone who enters a shared visitor password. Apps can be changed only on a server with app access turned on. An agent opens to public or password access only on a server with agent outside access turned on. Changing the mode revokes the access the old mode granted, so confirm the new mode with the user before calling. Requires connecting a Valet account.

Password mode does not take the password. The answer carries a request whose url the person opens, signed in to Valet, to set the shared visitor password; the mode changes only when they do. Say in reason why it needs a password. Give the person the url, then follow the request with get_request. Never ask for the password in this conversation. Otherwise the answer carries the access mode now in force and the url, version, and published_at of the live release when the service has one.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "mode": "<mode>"
    },
    "name": "set_service_access"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoThe kind you believe the named service is, as a safeguard against changing the wrong thing. Omit to change whatever the name holds.
modeYesWho may open the service from now on; the tool description says whom each mode lets in. Confirm the choice with the person first, because a narrower mode shuts out people who could open it before.
nameYesThe website's, app's, agent's, or skill's name, as list_services shows it: the one whose access to set.
reasonNoShown to the person on the request page to explain why the values are needed, so they can decide whether to enter them, such as: The site holds client drafts, so visitors need a password to open it.
org_nameNoThe Valet organization it belongs to. Omit to use the organization the account joined first.

Output Schema

NameRequiredDescriptionDefault
orgYesName of the Valet organization the call acted in.
urlNoAddress the service is served at. Absent when it has none, such as a service whose route is gone.
kindYesKind of the service: site, app, agent, or skill.
nameYesName of the service.
accessYesWho can reach the service: public, private, or password. Never includes the visitor password. While a password request is pending, the mode still in force.
requestNoThe request a person completes in the dashboard to enter a value that must not pass through this conversation. Absent when nothing needs a person.
versionNoVersion of the live release. Absent for a service nobody has published.
published_atNoRFC 3339 time the live release was created. Absent for a service nobody has published.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / reason / description
      Previous value: -"Why the request is made, in words the person reads on the request page before entering anything, so they know what the values are for, such as: The site holds client drafts, so visitors need a password to open it."New value: +"Shown to the person on the request page to explain why the values are needed, so they can decide whether to enter them, such as: The site holds client drafts, so visitors need a password to open it."
  2. Changed2 schema fields changed
    • changedInput schema / properties / mode / description
      Previous value: -"Who may open it. public is anyone with the link; private is members of the owning organization and anyone a member has shared it with through share_service; password is anyone who enters the shared visitor password, which a person sets on the request the answer carries."New value: +"Who may open the service from now on; the tool description says whom each mode lets in. Confirm the choice with the person first, because a narrower mode shuts out people who could open it before."
    • changedInput schema / properties / reason / description
      Previous value: -"Why the request is made, in the words the person reads on the request page, such as: The site holds client drafts, so visitors need a password to open it."New value: +"Why the request is made, in words the person reads on the request page before entering anything, so they know what the values are for, such as: The site holds client drafts, so visitors need a password to open it."
  3. Changed3 schema fields changed
    • changedInput schema / properties / kind / description
      Previous value: -"The kind you expect the name to hold. A name holding another kind is refused. Omit to change whatever the name holds."New value: +"The kind you believe the named service is, as a safeguard against changing the wrong thing. Omit to change whatever the name holds."
    • changedInput schema / properties / mode / description
      Previous value: -"public serves it to anyone who has the link. private serves it to members of the organization that owns it, and to anyone a member has shared it with through share_service. password serves it to anyone who enters the shared visitor password, which a person sets through the request the answer carries."New value: +"Who may open it. public is anyone with the link; private is members of the owning organization and anyone a member has shared it with through share_service; password is anyone who enters the shared visitor password, which a person sets on the request the answer carries."
    • changedInput schema / properties / reason / description
      Previous value: -"Why the request is made, in the words the person reads on the request page, such as: The site holds client drafts, so visitors need a password to open it. Give it with password mode; the other modes ignore it."New value: +"Why the request is made, in the words the person reads on the request page, such as: The site holds client drafts, so visitors need a password to open it."
  4. Changed2 schema fields changed
    • changedInput schema / properties / kind / description
      Previous value: -"The kind you mean. Omit to change whatever the name holds; give it to have a name holding another kind refused."New value: +"The kind you expect the name to hold. A name holding another kind is refused. Omit to change whatever the name holds."
    • changedInput schema / properties / reason / description
      Previous value: -"Give it with password mode; the other modes ignore it. Why the request is made, in the words the person reads on the request page, such as: The site holds client drafts, so visitors need a password to open it."New value: +"Why the request is made, in the words the person reads on the request page, such as: The site holds client drafts, so visitors need a password to open it. Give it with password mode; the other modes ignore it."
  5. Changed1 schema field changed
    • changedInput schema / properties / mode / description
      Previous value: -"public serves it 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, which a person sets through the request the answer carries."New value: +"public serves it to anyone who has the link. private serves it to members of the organization that owns it, and to anyone a member has shared it with through share_service. password serves it to anyone who enters the shared visitor password, which a person sets through the request the answer carries."
  6. Changed1 schema field changed
    • changedInput schema / properties / reason / description
      Previous value: -"Give it with password mode; the other modes ignore it. Why the value is needed, in the words the person reads on the request page, such as: The app charges cards and needs your Stripe key."New value: +"Give it with password mode; the other modes ignore it. Why the request is made, in the words the person reads on the request page, such as: The site holds client drafts, so visitors need a password to open it."
  7. Changed2 schema fields changed
    • changedInput schema / properties / name / description
      Previous value: -"The website's, app's, agent's, or skill's name to change."New value: +"The website's, app's, agent's, or skill's name, as list_services shows it: the one whose access to set."
    • changedInput schema / properties / reason / description
      Previous value: -"Give it with password mode; the other modes ignore it. One plain sentence, shown to the person on the request page, saying why the value is needed, such as: The app charges cards and needs your Stripe key."New value: +"Give it with password mode; the other modes ignore it. Why the value is needed, in the words the person reads on the request page, such as: The app charges cards and needs your Stripe key."
  8. Changed17 schema fields changed
    • changedInput schema / properties / mode / description
      Previous value: -"Required. The access mode. public serves it 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, which a person sets through the request the answer carries."New value: +"public serves it 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, which a person sets through the request the answer carries."
    • changedInput schema / properties / name / description
      Previous value: -"Required. The website's, app's, agent's, or skill's name."New value: +"The website's, app's, agent's, or skill's name to change."
    • changedInput schema / properties / reason / description
      Previous value: -"Required for password mode, ignored for the others. One plain sentence, shown to the person on the request page, saying why the value is needed, such as: The app charges cards and needs your Stripe key. At most 280 characters."New value: +"Give it with password mode; the other modes ignore it. One plain sentence, shown to the person on the request page, saying why the value is needed, such as: The app charges cards and needs your Stripe key."
    • addedOutput schema / properties / access / description
      Added value: +"Who can reach the service: public, private, or password. Never includes the visitor password. While a password request is pending, the mode still in force."
    • addedOutput schema / properties / kind / description
      Added value: +"Kind of the service: site, app, agent, or skill."
    • addedOutput schema / properties / name / description
      Added value: +"Name of the service."
    • addedOutput schema / properties / org / description
      Added value: +"Name of the Valet organization the call acted in."
    • addedOutput schema / properties / published_at / description
      Added value: +"RFC 3339 time the live release was created. Absent for a service nobody has published."
    • addedOutput schema / properties / request / description
      Added value: +"The request a person completes in the dashboard to enter a value that must not pass through this conversation. Absent when nothing needs a person."
    • addedOutput schema / properties / request / properties / expires_at / description
      Added value: +"When the request expires unanswered, as an RFC 3339 UTC time."
    • addedOutput schema / properties / request / properties / fields / description
      Added value: +"Names of what the person enters, never values."
    • addedOutput schema / properties / request / properties / id / description
      Added value: +"Id of the request. Pass it to get_request to follow the request."
    • addedOutput schema / properties / request / properties / next_step / description
      Added value: +"What to do next: give the person the url, then follow the request with get_request."
    • addedOutput schema / properties / request / properties / url / description
      Added value: +"Dashboard page to give the person. They open it signed in to Valet to complete the request. It holds no credential."
    • addedOutput schema / properties / url / description
      Added value: +"Address the service is served at. Absent when it has none, such as a service whose route is gone."
    • addedOutput schema / properties / version / description
      Added value: +"Version of the live release. Absent for a service nobody has published."
    • changedOutput schema / required
      Previous value: -[
      -  "org",
      -  "kind",
      -  "name",
      -  "access",
      -  "version"
      -]New value: +[
      +  "org",
      +  "kind",
      +  "name",
      +  "access"
      +]
  9. Changed4 schema fields changed
    • changedInput schema / properties / mode / description
      Previous value: -"Required. The access mode. public serves it 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 it 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, which a person sets through the request the answer carries."
    • removedInput schema / properties / password
      Removed value: -{
      -  "description": "The shared visitor password. Required for password mode and rejected for the others. Anyone who enters it can open the service, so its owner passes it to whoever should see it. At most 72 bytes.",
      -  "type": "string"
      -}
    • addedInput schema / properties / reason
      Added value: +{
      +  "description": "Required for password mode, ignored for the others. One plain sentence, shown to the person on the request page, saying why the value is needed, such as: The app charges cards and needs your Stripe key. At most 280 characters.",
      +  "maxLength": 280,
      +  "type": "string"
      +}
    • addedOutput schema / properties / request
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "expires_at": {
      +      "type": "string"
      +    },
      +    "fields": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": [
      +        "null",
      +        "array"
      +      ]
      +    },
      +    "id": {
      +      "type": "string"
      +    },
      +    "next_step": {
      +      "type": "string"
      +    },
      +    "url": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "id",
      +    "url",
      +    "expires_at",
      +    "fields",
      +    "next_step"
      +  ],
      +  "type": [
      +    "null",
      +    "object"
      +  ]
      +}
  10. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "access": {
      +      "type": "string"
      +    },
      +    "kind": {
      +      "type": "string"
      +    },
      +    "name": {
      +      "type": "string"
      +    },
      +    "org": {
      +      "type": "string"
      +    },
      +    "published_at": {
      +      "type": "string"
      +    },
      +    "url": {
      +      "type": "string"
      +    },
      +    "version": {
      +      "maximum": 2147483647,
      +      "minimum": -2147483648,
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "org",
      +    "kind",
      +    "name",
      +    "access",
      +    "version"
      +  ],
      +  "type": "object"
      +}
  11. Changed2 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."
  12. Changed2 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 or app's name."New value: +"Required. The website's, app's, or skill's name."
  13. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotent=true, but the description earns credit by naming the concrete destruction: changing the mode revokes the access the old mode granted. It also discloses the awkward two-step password flow (the mode does not change until the person opens the returned url) and the server toggles required for app and agent modes. The only small gap is that it doesn't warn about idempotency or repeat-call behavior, which annotations cover anyway.

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?

Front-loaded with the mode definitions and the revocation warning, then the password workflow, then the response shape — a logical order with no filler. The first sentence is overloaded with nested clauses describing private mode, which costs a little readability.

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 destructive, multi-mode tool with server-side preconditions and a deferred confirmation flow, the description covers everything an agent needs: preconditions, confirmation requirement, post-call follow-up, and what the answer contains. Return-value detail is partly redundant with the output schema but serves the conditional password branch.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning for two parameters: mode=password doesn't carry a password in the call, and reason must explain why a password is needed. The kind parameter's safeguard purpose is already in the schema, so the addition is modest rather than transformative.

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 and resource — 'Set who can reach a website, app, agent, or skill' — and then enumerates each mode's audience precisely. It is clearly distinguished from share_service, which grants per-person sharing, versus this tool's org-wide mode setting.

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?

Explicitly says to confirm the new mode with the user before calling because the old mode's access is revoked, and pins down the sibling workflow: give the person the url, then follow up with get_request. It also states the account prerequisite and server-level preconditions for app and agent modes.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources