agnes-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGNES_API_KEYS | Yes | JSON array of API keys, e.g. '["sk-xxx","sk-yyy"]' (overrides config.json) | |
| AGNES_BASE_URL | No | The API base URL for Agnes AI (overrides config.json) | https://apihub.agnes-ai.com/v1 |
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 |
|---|---|
| describe_imageA | Use this when you cannot directly read a local image. Reads a local image file and describes its content via Agnes AI vision model |
| generate_imageA | Generate an image from a text prompt (async). Returns taskId for status polling via get_task_status |
| generate_videoA | Generate a video from a text prompt (async). Returns taskId for status polling via get_task_status |
| get_task_statusA | Check the status of an async task (image generation or video generation). Queries cached result |
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 4 tools
Each tool serves a distinct purpose: describing images, generating images or videos asynchronously, and checking task status. No overlap in functionality.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., describe_image, generate_image), making the set predictable.
Four tools is well-scoped for the server's purpose of image/video generation and description, covering the essential operations without bloat.
The core workflow (generate async, poll status) is covered, but missing cancel or delete operations for tasks. Minor gap that agents can work around.