Skip to main content
Glama
geoffwhittington

SD Elements MCP Server

create_application

Create a new application in the SD Elements platform by defining its name, description, and associated business unit ID for secure development lifecycle management.

Instructions

Create a new application in SD Elements

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
business_unit_idNoID of the business unit this application belongs to
descriptionNoApplication description
nameYesApplication name

Implementation Reference

  • The MCP tool handler for 'create_application', decorated with @mcp.tool(). It constructs the application data from parameters, calls the internal API client to create the application, and returns the JSON result.
    @mcp.tool()
    async def create_application(ctx: Context, name: str, business_unit_id: int, description: Optional[str] = None) -> str:
        """Create a new application"""
        global api_client
        if api_client is None:
            api_client = init_api_client()
        data = {"name": name, "business_unit": business_unit_id}
        if description:
            data["description"] = description
        result = api_client.create_application(data)
        return json.dumps(result, indent=2)
  • The @mcp.tool() decorator registers the create_application function as an MCP tool.
    @mcp.tool()
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a creation operation, implying it's a write/mutation tool, but doesn't address critical aspects like required permissions, whether the operation is idempotent, what happens on duplicate names, or what the response contains (especially with no output schema). This leaves significant gaps for an agent to understand the tool's behavior.

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 wasted words. It's appropriately sized for a simple creation tool and front-loads the essential information.

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 this is a mutation tool (creation) with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns, error conditions, or behavioral constraints. For a tool that modifies system state, more context is needed to help an agent use it correctly and safely.

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 input schema has 100% description coverage, with clear documentation for all three parameters (business_unit_id, description, name). The description adds no additional parameter information beyond what's in the schema, so it meets the baseline of 3 where the schema does the heavy lifting without compensating for any gaps.

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 action ('Create') and resource ('new application in SD Elements'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'create_project' or 'update_application', which would require specifying what distinguishes an 'application' from a 'project' in this context.

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. It doesn't mention prerequisites (e.g., needing a business unit ID), when not to use it (e.g., for updating existing applications), or direct alternatives like 'update_application' or 'create_project' from the sibling list.

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