etsySellerAssistant
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_setup_statusA | Reports local setup status. This scaffold does not connect to Etsy or read shop data. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
There is only one tool, so there is no potential overlap or misselection. Its purpose, reporting local setup status, is clearly stated.
The single tool uses a readable snake_case verb_noun pattern: get_setup_status. There is no broader set to demonstrate consistency, but the name itself is clear.
A single setup-status tool is extremely thin for an Etsy seller assistant. It appears to be a scaffold rather than a usable tool surface.
The tool explicitly does not connect to Etsy or read shop data. There are no listing, shop, order, inventory, or seller-management operations, leaving the stated domain almost entirely uncovered.