Skip to main content
Glama
severity1

argocd-mcp

by severity1
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

get_plugins

Retrieve a list of available plugins in ArgoCD using the api/v1/settings/plugins endpoint to manage and integrate plugins effectively.

Instructions

Get returns Argo CD plugins using api/v1/settings/plugins

This endpoint returns information about available plugins in ArgoCD.

Returns:
    List of available plugins

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • tools/settings.py:27-43 (handler)
    The handler function implementing the get_plugins tool logic. Fetches ArgoCD plugins from the /api/v1/settings/plugins endpoint using make_api_request and returns the data or error.
    async def get_plugins() -> Dict[str, Any]:
    """
    Get returns Argo CD plugins using api/v1/settings/plugins

    This endpoint returns information about available plugins in ArgoCD.

    Returns:
        List of available plugins
    """
    success, data = await make_api_request("settings/plugins")

    if success:
        # Return the full plugins response
        return data
    else:
        # Return a properly structured error dictionary
        return {"error": data.get("error", "Failed to retrieve ArgoCD plugins")}
  • server.py:35-35 (registration)
    Registration of the get_plugins tool using the FastMCP tool decorator.
    mcp.tool()(settings.get_plugins)

Tool Definition Quality

B3.1/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It states the tool returns a list of plugins but doesn't disclose behavioral traits such as authentication requirements, rate limits, error handling, or whether it's read-only (implied by 'Get' but not explicit). It lacks details on response format, pagination, or side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized with three sentences: it states the action, clarifies the endpoint, and notes the return value. It's front-loaded with the core purpose. However, the first sentence is slightly redundant ('Get returns'), and the 'Returns:' section could be integrated more smoothly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate. It covers what the tool does and the return type but lacks context on usage, behavior, or integration with siblings. For a read-only tool with no params, it's passable but could benefit from more guidance or transparency.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add param info, but with no params, this is acceptable. It implies no filtering or input is required, which aligns with the empty schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Get returns Argo CD plugins using api/v1/settings/plugins' and 'This endpoint returns information about available plugins in ArgoCD.' It specifies the verb ('Get'), resource ('Argo CD plugins'), and endpoint, though it doesn't explicitly differentiate from siblings like 'get_settings' or 'get_user_info' beyond the resource type.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. The description mentions the endpoint but doesn't explain its context relative to sibling tools (e.g., 'get_settings' might include plugin info, or 'list_applications' could relate). There's no mention of prerequisites, timing, or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/severity1/argocd-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server