impart-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENT_CONFIG_PATH | No | Path to agent configuration JSON file |
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 | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| call_agentA | Synchronous single agent call (BLOCKING, 30-120s). ⚠️ STOP: Choose the Right Tool FirstDecision Tree:
Why async for search agents?
Available Agents
Agent → Tool Mapping
| ||||||||||||||||||
| call_agent_asyncA | Start agent task in background (NON-BLOCKING). Returns task_id immediately. ✅ Recommended for explore/researcherWorkflow:
Why async is better:
Parallel search pattern: | ||||||||||||||||||
| get_agent_resultA | Get result from async agent task. Parameters:
Returns task status and result if completed. | ||||||||||||||||||
| call_agents_batchA | Execute multiple agents in PARALLEL (BLOCKING until ALL complete). ⚠️ Usually NOT what you wantPrefer
Only use batch when:
Example (usually wrong): ↑ This blocks until both finish. Use call_agent_async × 2 instead. Example (correct use case): Comparing outputs from multiple agents where you need all results simultaneously. |
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
The tools are functionally distinct by execution model (sync, async, batch, result retrieval), but call_agent_async and call_agents_batch overlap in parallel execution capability, requiring extensive warnings to steer usage. The descriptions clarify intent, but the ambiguity is notable enough to deduct a point.
All tools follow a snake_case verb_noun pattern with clear prefixes (call_, get_). However, the distinction between call_agent, call_agent_async, and call_agents_batch is subtle, and pluralization is inconsistent, slightly reducing predictability.
Four tools is an appropriate scope for an agent orchestration server, covering the essential sync, async, batch, and result retrieval patterns without bloat or redundancy. Each tool serves a distinct purpose in the workflow.
The surface covers the core lifecycle of launching and retrieving agent results, including synchronous and asynchronous execution. Missing cancellation or task listing is a minor gap, but the main workflows are well-supported.