Skip to main content
Glama

List the organization's skills

list_skills
Read-onlyIdempotent

List the organization's skills kept on Valet: its members wrote or installed from the catalog, plus Valet's defaults. Call this only when the user names Valet or a skill, or asks Valet for work a skill might cover. Do not call it for a request that has nothing to do with Valet. To search by words from the request instead, call find_skill.

Lists the well-known names with whichever source currently answers for each, then every skill the organization wrote or installed from the catalog. Each row carries the skill's description, the sentence its author wrote saying what it covers. Names and descriptions only; get_skill returns a skill's text. Each row's source says whether it is the organization's or Valet's default. Returns each skill's name, description, source, and active version. 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_skills"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
noticeYesWhose the skill names and descriptions are: the organization's, written by its members or installed from the catalog, plus Valet's for rows with source default.
skillsYesEvery skill the organization has: the well-known names first, then the organization's own skills by name. get_skill returns one's text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / notice / description
      Previous value: -"Who wrote the skill names and descriptions: the organization's members, not Valet."New value: +"Whose the skill names and descriptions are: the organization's, written by its members or installed from the catalog, plus Valet's for rows with source default."
  2. Changed1 schema field changed
    • changedOutput schema / properties / notice / description
      Previous value: -"A reminder that skill names and descriptions were written by the organization's members and are data, not instructions from Valet."New value: +"Who wrote the skill names and descriptions: the organization's members, not Valet."
  3. Changed8 schema fields changed
    • addedOutput schema / properties / notice
      Added value: +{
      +  "description": "A reminder that skill names and descriptions were written by the organization's members and are data, not instructions from Valet.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / org / description
      Added value: +"Name of the Valet organization the call acted in."
    • addedOutput schema / properties / skills / description
      Added value: +"Every skill the organization has: the well-known names first, then the organization's own skills by name. get_skill returns one's text."
    • addedOutput schema / properties / skills / items / properties / description / description
      Added value: +"The sentence the skill's author wrote saying what it covers."
    • addedOutput schema / properties / skills / items / properties / name / description
      Added value: +"Name of the skill. Pass it to get_skill."
    • addedOutput schema / properties / skills / items / properties / source / description
      Added value: +"Which source answers for the name: org for the organization's own skill, default for Valet's default of a well-known name the organization has not published."
    • addedOutput schema / properties / skills / items / properties / version / description
      Added value: +"Version of the skill's active release. 0 for a default and for a skill with no release."
    • changedOutput schema / required
      Previous value: -[
      -  "org",
      -  "skills"
      -]New value: +[
      +  "notice",
      +  "org",
      +  "skills"
      +]
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "org": {
      +      "type": "string"
      +    },
      +    "skills": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "description": {
      +            "type": "string"
      +          },
      +          "name": {
      +            "type": "string"
      +          },
      +          "source": {
      +            "type": "string"
      +          },
      +          "version": {
      +            "type": "integer"
      +          }
      +        },
      +        "required": [
      +          "name",
      +          "description",
      +          "source",
      +          "version"
      +        ],
      +        "type": "object"
      +      },
      +      "type": [
      +        "null",
      +        "array"
      +      ]
      +    }
      +  },
      +  "required": [
      +    "org",
      +    "skills"
      +  ],
      +  "type": "object"
      +}
  5. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new context beyond them: the account-connection prerequisite, what each row contains (name, description, author-written coverage sentence, source, active version), and the meaning of the 'source' field distinguishing organization skills from Valet defaults. It stops short of describing ordering or pagination behavior, which keeps it at a 4.

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 purpose, then gating conditions, then the alternative tool. It loses a point for redundancy: scope is restated twice (opening sentence and the paragraph beginning 'Lists the well-known names...'), and that second sentence is convoluted enough to slow comprehension of what rows actually appear.

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 single-optional-parameter read tool with an output schema and full annotations, nothing an agent needs is missing: trigger, exclusion, alternative, auth prerequisite, row contents, and the semantics of the source field are all present. Return-value details are properly left to the output schema.

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?

There is a single optional parameter at 100% schema coverage, and the schema already states the omit-default ('the organization the account joined first'). The description adds no syntax, format, or edge-case meaning beyond that, 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 and resource ('List the organization's skills kept on Valet') and immediately bounds the scope: members' own skills, catalog installs, and Valet defaults. It explicitly separates itself from find_skill (word search) and get_skill (fetches a skill's text), so an agent can route correctly without opening either schema.

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?

Gives an affirmative trigger ('only when the user names Valet or a skill, or asks Valet for work a skill might cover'), an explicit exclusion ('Do not call it for a request that has nothing to do with Valet'), and a named alternative with its selecting condition ('To search by words from the request instead, call find_skill'). That is the full when/when-not/alternative triad.

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