Retrieve Endpoint Groups (EPGs) from Cisco APIC, optionally filtered by tenant, to obtain EPG details including tenant, application, name, description, and policy information.
Retrieve Endpoint Groups (EPGs) from APIC.
Args:
tenant: Optional tenant name filter. If not specified, returns EPGs from all tenants.
Returns EPGs with tenant, application, name, description, and policy details.
| Name | Required | Description | Default |
|---|---|---|---|
| tenant | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Description implies a read-only operation ('Retrieve') but with no annotations, it offers no additional details on authorization, rate limits, or side effects. Adequate for a simple get tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three concise sentences with no wasted words. Front-loaded with the primary purpose, followed by parameter details and return info.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Reasonably complete for a simple read-only tool: it covers purpose, filter parameter, and return content. Lacks potential details like pagination, but not critical here.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 0% schema description coverage, the description adds essential meaning: the tenant parameter is an optional filter, and explains the default behavior when omitted.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool retrieves Endpoint Groups (EPGs) from APIC, with a specific verb and resource. It also lists the return content, distinguishing it from siblings like apic_get_epg_endpoints.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides clear context for the optional tenant parameter and default behavior, but does not explicitly compare to alternatives or state when not to use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/angoran/git-netai'
If you have feedback or need assistance with the MCP directory API, please join our Discord server