Skip to main content
Glama
geoffwhittington

SD Elements MCP Server

list_applications

Retrieve all applications in SD Elements with options to paginate, include additional fields, or expand specific details for comprehensive access.

Instructions

List all applications in SD Elements

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
expandNoFields to expand (comma-separated)
includeNoAdditional fields to include (comma-separated)
page_sizeNoNumber of results per page (optional)

Implementation Reference

  • The handler function for the 'list_applications' MCP tool. It initializes the API client if necessary, builds query parameters, calls the API to list applications, and returns the result as formatted JSON. The @mcp.tool() decorator registers it as an MCP tool, and the function signature with docstring defines the input schema.
    @mcp.tool()
    async def list_applications(ctx: Context, page_size: Optional[int] = None, include: Optional[str] = None, expand: Optional[str] = None) -> str:
        """List all applications"""
        global api_client
        if api_client is None:
            api_client = init_api_client()
        params = build_params({"page_size": page_size, "include": include, "expand": expand})
        result = api_client.list_applications(params)
        return json.dumps(result, indent=2)
  • Import of the tools package in the main server.py, which transitively imports tools/applications.py and registers all tools including 'list_applications'.
    from . import tools  # noqa: F401
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action without disclosing behavioral traits. It doesn't mention whether this is a read-only operation, if it requires authentication, rate limits, pagination behavior beyond the 'page_size' parameter, or what the return format looks like. This is inadequate for a tool with zero annotation coverage.

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

Conciseness5/5

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

The description is a single, efficient sentence that directly states the tool's purpose without any unnecessary words. It's appropriately sized and front-loaded, making it easy for an agent to parse quickly.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'applications' are in this context, how results are returned (e.g., list format, pagination details), or error conditions. For a tool with three parameters and no structured output information, more context is needed.

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

Parameters3/5

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

The schema description coverage is 100%, so the schema already documents all three parameters ('expand', 'include', 'page_size') with their types and descriptions. The description adds no additional parameter information beyond what the schema provides, resulting in the baseline score of 3.

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 verb ('List') and resource ('all applications in SD Elements'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_application' (singular) or 'list_projects' (different resource), which prevents a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives like 'get_application' for a single application or 'list_projects' for different resources. There's no mention of prerequisites, context, or exclusions, leaving the agent with minimal usage direction.

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/geoffwhittington/sde-mcp'

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