Overview
Agents in Solace Agent Mesh are configured using YAML files that define their behavior, capabilities, and integration points. Each agent configuration controls everything from LLM models to tool integrations and session management.Complete Configuration Schema
Top-Level App Configuration
Core Agent Properties
The A2A topic namespace (e.g., “myorg/dev”). Must be set via
${NAMESPACE} environment variable.Unique identifier for the agent within the mesh. Used for agent discovery and routing.
Human-readable name shown in UI components.
Whether the agent supports streaming responses. Set to
false for tool-only agents.Model Configuration
Defines the LLM model to use for agent reasoning.Subfields:
provider(string, required): LLM provider (“google”, “openai”, “anthropic”, etc.)model_name(string, required): Specific model identifiertemperature(float): Sampling temperature (0.0-1.0)max_tokens(integer): Maximum output tokens
Instructions
System prompt that defines the agent’s behavior and capabilities.
Tool Configuration
Tools Definition
List of tools available to the agent. Supports built-in tools, MCP servers, and custom tools.
MCP Tool Configuration
Set to
"mcp" for Model Context Protocol tools.Optional: Specific tool name from the MCP server. If omitted, all tools from the server are loaded.
MCP server connection configuration:
type(string): Connection type ("stdio"or"sse")command(string): Command to launch the MCP server (for stdio)args(array): Command argumentstimeout(integer): Connection timeout in secondsurl(string): Server URL (for SSE connections)
Environment variables to pass to the MCP server process.
Built-in Tool Groups
Available built-in tool groups:artifact_management: Create, read, update, delete, and list artifactsdata_analysis: Analyze data from artifacts (CSV, JSON, etc.)
Service Configuration
Session Service
Configures conversation history storage.Types:
memory: In-memory storage (ephemeral)database: SQLite/PostgreSQL storage (persistent)
PERSISTENT: Maintains conversation history across requestsRUN_BASED: Each request is independent
Artifact Service
Configures file/artifact storage backend.Artifact Scopes:
namespace: Shared across all agents in the namespacesession: Isolated per user sessionagent: Isolated per agent
Advanced Configuration
Artifact Handling
How artifacts are passed to the LLM:
reference: Only metadata passed (recommended)inline: Full content embedded in context
Enable dynamic embed resolution (e.g.,
{{artifact:filename.txt}}).Include artifact content summaries in system instructions.
Tool Output Management
Automatically save tool outputs larger than this size as artifacts.
Maximum tool output size to return to LLM. Larger outputs are truncated and saved as artifacts.
MCP Response Handling
Automatically save MCP responses larger than this size as artifacts.
Maximum MCP response size to return to LLM.
Binary Content Extraction
Configure LLM-powered extraction from binary files (images, PDFs).
Agent Card
Metadata for agent discovery and routing.
Agent Card Publishing
Configure agent discovery broadcasting.
Agent Discovery
Enable discovery of peer agents in the mesh.
Inter-Agent Communication
Configure peer-to-peer agent communication.Subfields:
allow_list(array): Agents this agent can call (empty = all allowed)request_timeout_seconds(integer): Timeout for peer requests
Auto-Summarization
Configure automatic context window management.
Complete Example
agent-config.yaml
Environment Variables
Required environment variables for agent configuration:NAMESPACE: A2A topic namespaceSOLACE_BROKER_URL: Solace broker connection URLSOLACE_BROKER_USERNAME: Broker usernameSOLACE_BROKER_PASSWORD: Broker passwordSOLACE_BROKER_VPN: Broker VPN nameGOOGLE_API_KEY: Google AI API key (if using Gemini models)- LLM-specific API keys as needed
See Also
- Agent Lifecycle - Understand agent startup and shutdown
- Agent Callbacks - Customize agent behavior with callbacks
- Tool Development - Create custom tools for agents