Skip to main content
Glama

Valet

by io.github.valetdotdev
OverviewDiscussionsAdmin

Get a skill

get_skill
Read-onlyIdempotent

Get one skill by name: the organization's own when it has published one under that name, otherwise the default Valet supplies for a well-known name. Call it with governance before any work and again before any publish; that skill says what the organization expects and names the other skills to read. Call it with any name list_skills reports, or any name the governance skill tells you to read.

The result says where the skill came from. source: org is the organization's own content and overrides anything Valet would have said. source: default is Valet's, returned because the organization has not written its own; for design-system it is the preset the organization selected, and reason says why a selection could not be honored when one could not. Supporting files are listed by path; read one by calling get_skill again with the same skill and that path. A skill's SKILL.md says which files to read; do not read every file on principle. Binary files are listed but not returned.

By default this requires a connected account. Pass anonymous: true only when building an explicitly anonymous site; no organization is then consulted, and only a well-known name has an answer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoThe path of one supporting file to read instead of the skill's SKILL.md, as an earlier get_skill listed it. Omit to read the skill itself.
skillYesRequired. The skill's name: governance, design-system, or any name list_skills reports.
org_nameNoThe Valet organization whose skill to read. Omit to use the organization the account joined first.
anonymousNoSet true only when building an explicitly anonymous site. No organization is consulted and Valet's default is returned. Omit for the account-first path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / properties / name
      Removed value: -{
-  "description": "Required. The skill's name: governance, design-system, or any name list_skills reports.",
-  "type": "string"
-}
    • addedInput schema / properties / path
      Added value: +{
+  "description": "The path of one supporting file to read instead of the skill's SKILL.md, as an earlier get_skill listed it. Omit to read the skill itself.",
+  "type": "string"
+}
    • addedInput schema / properties / skill
      Added value: +{
+  "description": "Required. The skill's name: governance, design-system, or any name list_skills reports.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "name"
-]New value: +[
+  "skill"
+]
  2. Added

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare a safe, idempotent, non-destructive read (readOnlyHint, idempotentHint, destructiveHint=false), so the safety profile is covered. The description nonetheless adds meaningful behavior beyond them: source resolution, the connected-account requirement, the anonymous override, and that binary files are listed but not returned. This is a genuine value-add, but much of the surface-level 'what happens' is already implied by annotations, so a 3 is appropriate; return pagination/format remains unstated.

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?

Four short paragraphs are front-loaded with the core purpose and each block (resolution, return shape, auth) earns its place. It is dense but not padded, though it sits near the upper end of what an agent needs to read before calling.

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 still explains the return surface: the source/org-vs-default provenance, the reason field, supporting files listed by path, and the binary-file caveat. Auth prerequisites and the anonymous exception are stated, so an agent has everything needed to call correctly.

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. The description exceeds that by clarifying the recursive read pattern (re-invoke with the same skill plus a supporting-file path) and by adding the constraint that under anonymous only a well-known name has an answer, a nuance not present in the schema's enum-free param descriptions.

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 ('Get one skill by name') and immediately defines the resolution rule (org's own content vs. Valet's default by name). It is clearly distinguishable from list_skills, publish_skill, and attach_skill, which the description and sibling list make obvious.

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 explicit when-to-use instructions ('Call it with governance before any work and again before any publish') and names the alternatives that feed it ('any name list_skills reports, or any name the governance skill tells you to read'). The anonymous-vs-connected path is also conditionally scoped.

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
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources