Skip to main content
Glama
Sign In

Valet

by io.github.valetdotdev
OverviewDiscussionsAdmin

Get a website, app, agent, or skill

get_service
Read-onlyIdempotent

Get one website, app, agent, or skill by name. The result carries the fields every kind has, then a section for its kind. A website: access mode, the people it is shared with, and attached connectors. An app: each process type with its scale and current state, attached resources with their state, environment variable names, the active release, and the people it is shared with. An agent: its URL, access mode, the people it is shared with, channels, connectors, declared skills, and blueprint state. A skill: its description, where it came from, the agents it is attached to, its author, whether the organization starred it, and the people it is shared with. Every kind: whether a draft is open and who opened it. Fields another kind would have are absent.

A website, app, agent, or skill reports its access mode: private, password, or public. A shared website, app, agent, or skill lists each recipient's email, as the dashboard does. A password-protected service reports that it is gated and never its visitor password. Identify it by name, which requires connecting a Valet account, or, for a website published anonymously, by the site_token that publish returned.

Input Schema

NameRequiredDescriptionDefault
nameNoGive this or site_token. The service's name, which requires a connected Valet account.
org_nameNoThe Valet organization it belongs to. Omit to use the organization the account joined first.
site_tokenNoGive this or name. The token returned when the site was published anonymously; it identifies that one site.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare read-only/idempotent/non-destructive, and the description adds real context on top: the per-kind return shape, that other kinds' fields are absent, the enumerated access modes, and the important security guarantee that a gated service reports gating but never the visitor password.

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-loads purpose and identification rules, then enumerates return fields per kind. The enumeration is long but each sentence carries distinct information; the structure is sound even if dense.

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?

There is no output schema, so the description must carry return-value semantics, and it does so thoroughly per service kind plus shared behaviors like draft state and recipient listing. An agent knows what to expect after calling.

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% and the schema already documents name, org_name, and site_token including the account requirement and the org default. The description largely restates that, adding only the 'published anonymously' framing for site_token, so 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?

Opens with a specific verb and resource set: 'Get one website, app, agent, or skill by name.' That clearly separates it from list_services (many), create_service, and the kind-specific get_skill/get_connector siblings.

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?

Explains the two identification paths and their preconditions: name requires a connected Valet account, site_token covers anonymously published sites. It does not address when to prefer this over the overlapping get_skill or get_connector siblings, which is the main missing piece.

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