Claude Asset Tagging Agent
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 |
|---|---|
| list_drive_filesA | List up to 15 files inside a specific Google Drive folder. |
| tag_drive_fileA | Star a file and add AI-generated category and tags to its Drive description. |
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 2 tools
The two tools have entirely distinct purposes: listing files in a folder versus tagging a specific file. There is no ambiguity or overlap.
Both tool names follow a consistent verb_noun pattern (list_drive_files, tag_drive_file) using snake_case, making them predictable and clear.
With only two tools, the server feels minimal but still reasonably scoped for a focused tagging agent. It just barely covers the core actions, though more tools might be expected for a richer workflow.
The domain is Google Drive file tagging, and the tools cover listing and tagging. However, missing operations like untagging, updating tags, or searching tagged files leave notable gaps for a complete tagging workflow.