Skip to main content
Glama

List websites, apps, agents, and skills

list_services
Read-onlyIdempotent

List websites, apps, agents, and skills: every one the organization has, with its kind, URL, access mode, and when it was last published. It is the first read when the user names something on Valet and you do not know what it is, and the way to recover a name an earlier publish has scrolled out of the conversation. The answer also says how many matched and whether the list was cut. Valet's built-in skills are not listed until the organization makes its own; list_skills lists those. Returns each service's name, kind, URL, access, active release, and when it was last published, with total and truncated. Requires connecting a Valet account.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_services"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoThe one kind of service to list, for when the person asks only about their agents or only about their sites. Omit to list everything the organization has.
org_nameNoThe Valet organization to list. Omit to use the organization the account joined first.

Output Schema

NameRequiredDescriptionDefault
orgYesName of the Valet organization the call acted in.
totalYesHow many services matched, which is more than the length of services only when truncated is true.
servicesYesThe services, sorted by name. Holds the first ones only when truncated is true.
truncatedYesTrue when the list was cut, so services holds only the first matches by name. Pass kind to narrow it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / kind / description
      Previous value: -"Use it when the person asks about one kind, such as only their agents, to keep the answer short. Omit to list everything the organization has."New value: +"The one kind of service to list, for when the person asks only about their agents or only about their sites. Omit to list everything the organization has."
  2. Changed1 schema field changed
    • changedInput schema / properties / kind / description
      Previous value: -"Narrow the list to one kind of service. Omit to list them all."New value: +"Use it when the person asks about one kind, such as only their agents, to keep the answer short. Omit to list everything the organization has."
  3. Changed1 schema field changed
    • changedInput schema / properties / kind / description
      Previous value: -"Only services of this kind. Omit to list every website, app, agent, and skill."New value: +"Narrow the list to one kind of service. Omit to list them all."
  4. Changed2 schema fields changed
    • changedInput schema / properties / kind / description
      Previous value: -"Narrow the list to one kind. Omit for everything."New value: +"Only services of this kind. Omit to list every website, app, agent, and skill."
    • changedOutput schema / properties / services / items / required
      Previous value: -[
      -  "name",
      -  "kind"
      -]New value: +[
      +  "name",
      +  "kind",
      +  "access"
      +]
  5. Changed10 schema fields changed
    • addedOutput schema / properties / org / description
      Added value: +"Name of the Valet organization the call acted in."
    • addedOutput schema / properties / services / description
      Added value: +"The services, sorted by name. Holds the first ones only when truncated is true."
    • addedOutput schema / properties / services / items / properties / access / description
      Added value: +"Who can reach the service: public, private, or password."
    • addedOutput schema / properties / services / items / properties / active_release / description
      Added value: +"Version of the live release. Absent for a service nobody has published."
    • addedOutput schema / properties / services / items / properties / kind / description
      Added value: +"site, app, agent, or skill."
    • addedOutput schema / properties / services / items / properties / last_published_at / description
      Added value: +"RFC 3339 time the live release was created. Absent for a service nobody has published."
    • addedOutput schema / properties / services / items / properties / name / description
      Added value: +"Name of the service. Pass it as name to the other service tools."
    • addedOutput schema / properties / services / items / properties / url / description
      Added value: +"Address the service is served at. Absent when it has none, such as a service whose route is gone, and for an agent in an organization whose agent URLs are not turned on."
    • addedOutput schema / properties / total / description
      Added value: +"How many services matched, which is more than the length of services only when truncated is true."
    • addedOutput schema / properties / truncated / description
      Added value: +"True when the list was cut, so services holds only the first matches by name. Pass kind to narrow it."
  6. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "org": {
      +      "type": "string"
      +    },
      +    "services": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "access": {
      +            "type": "string"
      +          },
      +          "active_release": {
      +            "maximum": 2147483647,
      +            "minimum": -2147483648,
      +            "type": "integer"
      +          },
      +          "kind": {
      +            "type": "string"
      +          },
      +          "last_published_at": {
      +            "type": "string"
      +          },
      +          "name": {
      +            "type": "string"
      +          },
      +          "url": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "name",
      +          "kind"
      +        ],
      +        "type": "object"
      +      },
      +      "type": [
      +        "null",
      +        "array"
      +      ]
      +    },
      +    "total": {
      +      "type": "integer"
      +    },
      +    "truncated": {
      +      "type": "boolean"
      +    }
      +  },
      +  "required": [
      +    "org",
      +    "services",
      +    "total",
      +    "truncated"
      +  ],
      +  "type": "object"
      +}
  7. Changed1 schema field changed
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "site",
      -  "app",
      -  "agent"
      -]New value: +[
      +  "site",
      +  "app",
      +  "agent",
      +  "skill"
      +]
  8. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the read-only, idempotent, non-destructive annotations, the description adds that it lists every service the organization has, that built-in skills are excluded until the organization makes its own, and that results include total and truncated fields. It also states the account-connection requirement and mentions the returned fields, which is useful behavioral context for a read operation.

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 key usage context. It is a little repetitive because it mentions kind, URL, access, and last published in the first sentence and again in the returns sentence, but overall it remains clear and reasonably structured.

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 the annotations and output schema, the description supplies the important missing context: organization-wide scope, built-in skill exclusion, truncation signaling, and the need to connect a Valet account. An agent has enough information to call this tool correctly and interpret the scope of the result.

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 description coverage is 100%, so the schema already explains the kind enum and org_name omission behavior. The description reinforces organization-level scoping and kind filtering but does not add syntax or format details beyond what the schema provides, so the 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 gives a specific verb and resource: list websites, apps, agents, and skills with kind, URL, access mode, and last publish time. It clearly distinguishes this broad service listing from list_skills, which handles built-in skills, so an agent can tell which tool to select without opening the schema.

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?

It says to use this first when the user names something on Valet and the agent does not know what it is, and as a way to recover a name that scrolled out of the conversation. It also names list_skills as the alternative for built-in skills. However, it does not explicitly state when not to use this tool beyond that skill distinction.

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