agntcy-mcp-server
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| tool_register_agntcy_agentB | Register an agent in the local AGNTCY-compatible directory. Creates an AGNTCY Directory Entry with ACP-compatible profile. The agent becomes discoverable via discover_by_capability. Args: name: Agent name (e.g. "DataAnalysisAgent") description: What the agent does capabilities: List of capabilities (e.g. ["data-analysis", "web-search"]) endpoint: URL or address where the agent is reachable organization: Optional: organization behind the agent |
| tool_discover_by_capabilityB | Find AGNTCY agents by capability in the local directory. Searches registered agents by capabilities, name and description. Ideal for task routing and agent selection in multi-agent systems. Args: capability: Capability to search for (e.g. "data-analysis", "translation") limit: Max number of results (default: 10) |
| tool_create_acp_messageA | Create an ACP-compliant message (Agent Communication Protocol v1.14). ACP is the AGNTCY standard for structured agent-to-agent communication. Message types: request, response, notification, error. Args: sender_id: ID or name of the sending agent receiver_id: ID or name of the receiving agent content: Message content message_type: Message type: "request", "response", "notification", "error" thread_id: Optional thread ID for multi-turn conversations |
| tool_validate_acp_messageC | Validate an ACP message against the v1.14 specification. Checks required fields, types and formatting against the AGNTCY Agent Communication Protocol standard. Args: message: ACP message as dictionary |
| tool_format_slim_messageB | Format a SLIM message (Secure Low-latency Interactive Messaging). SLIM is the AGNTCY protocol for secure real-time agent communication. Supports pub-sub, end-to-end encryption and low latency. Args: sender_id: ID of the sending agent channel: SLIM channel (e.g. "tasks/analysis", "alerts/security") payload: Message content encrypted: Whether to encrypt the message (default: True) |
| tool_get_agntcy_network_infoA | Get information about the AGNTCY network and ecosystem. Shows protocol versions, member organizations, SDKs and current stats of the AGNTCY multi-agent network (Linux Foundation project, 65+ members). |
| tool_list_agntcy_agentsA | List all locally registered AGNTCY agents. Shows all agents in the local AGNTCY directory with optional filter by capability or organization. Args: filter_capability: Optional: only show agents with this capability filter_org: Optional: only show agents from this organization |
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 7 tools
Most tools have distinct purposes, but list_agntcy_agents and discover_by_capability both involve searching agents by capability, creating potential confusion. Descriptions help differentiate (listing all vs. searching by capability), but overlap reduces clarity.
Tool names follow a consistent verb_noun pattern (e.g., create_acp_message, register_agntcy_agent). However, discover_by_capability deviates by including a preposition, and some names use 'agntcy' while others use 'ACP' or 'SLIM', showing minor inconsistency.
With 7 tools covering message creation, validation, agent registration, discovery, and network info, the count is well-scoped for an agent communication server. No tools feel redundant or excessive.
The set covers core functionality (message create/validate, agent register/discover) but lacks update/delete for agents and send/receive for messages. These gaps limit full lifecycle management, though they may be intentional for a client-side library.