Content Plan Builder
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANTHROPIC_API_KEY | Yes | Anthropic API key for Claude |
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 |
|---|---|
| plan_from_contentA | Generate Asana project plans from arbitrary content (text, PDF, DOCX, transcripts). This tool accepts various input types and uses AI to create comprehensive project plans with:
Operations:
Call without parameters for interactive discovery. |
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
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'plan_from_content' has a single, clearly defined purpose of generating Asana project plans from content, making disambiguation perfect.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'plan_from_content' follows a clear verb_noun pattern (plan from content), and there are no other tools to cause inconsistency.
A single tool for a server named 'Content Plan Builder' feels too thin for the apparent scope. The tool handles multiple operations (generate, preview, create), but these are bundled into one tool, suggesting the server might be under-scoped. Typically, such operations could be separate tools for better modularity and clarity.
The tool covers core generation and creation operations for Asana project plans, but there are notable gaps. For example, there are no tools for updating, deleting, or managing existing plans, which are common in project management domains. This could lead to dead ends for agents trying to modify or remove plans.