PixelVault
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_assetsA | Search PixelVault for pre-cleared, commercially licensed AI-generated assets matched to a creative brief. Every asset is sourced from licensed AI platforms (Adobe Firefly, Moonvalley) and carries a compliance-cleared status. Returns a ranked shortlist with compliance status, format, platform, and rationale. |
| get_asset_detailsB | Get full metadata and compliance documentation for a specific PixelVault asset by ID. |
| generate_usage_agreementA | Generate a usage agreement document for approved PixelVault assets. Call after human approval of a shortlist. |
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 3 tools
Each tool has a distinct purpose: search assets, get details, and generate agreement. No overlap.
All tools follow a consistent verb_noun pattern with snake_case, e.g., search_assets, get_asset_details, generate_usage_agreement.
Three tools are well-scoped for the asset management workflow; each tool serves a clear role without unnecessary bulk.
The tools cover the full lifecycle for the stated purpose: search, retrieve details, and generate an agreement. No missing operations.