Skip to main content
Glama

Create application

create_application
Destructive

Create an Application from a connected git repository: the platform links the repo/branch under the named git credential and provisions the CI/CD pipeline. The credential is referenced BY NAME - never pass secret values.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "repo_credential_name": "<repo_credential_name>",
      "repo_owner": "<repo_owner>",
      "repo_name": "<repo_name>",
      "repo_branch": "<repo_branch>"
    },
    "name": "create_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesApplication name, unique within the organisation.
repo_nameYesRepository name.
repo_ownerYesRepository owner/organisation.
repo_branchYesBranch the application builds from.
repo_credential_nameYesName of the git credential that grants access to the repository.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and idempotentHint=false, so the mutation profile is known. The description adds useful side-effect context (CI/CD pipeline provisioning) and the no-secrets rule, but leaves unclear why a create is marked destructive, whether re-running with the same name fails or duplicates, and what is returned.

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?

Two tight sentences with the mechanism first and the security caveat second; nothing is padded or repeated from the title or schema.

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?

For a non-idempotent, destructive-flagged creation that provisions infrastructure, the description omits the return value (no output schema exists) and the duplicate-name behavior, despite the schema noting the name is unique per organisation. It covers prerequisites and side effects adequately but not outcomes.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds a real constraint beyond the schema: the credential is passed BY NAME and secret values must never be supplied. That is a meaningful semantic rule the schema's field description does not convey as forcefully.

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 gives a specific verb and resource ('Create an Application') plus the mechanism: it links the repo/branch under a named git credential and provisions the CI/CD pipeline. That distinguishes it well from unrelated create_* siblings by resource, though it does not explicitly contrast with adjacent tools like create_pipeline_schedule or create_project.

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

Usage Guidelines3/5

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

Usage context is implied rather than stated: the caller learns the repo must be connected and the credential must already exist under a name, which functions as an implicit prerequisite. There is no explicit 'use this when...' or exclusion guidance, and no mention of what to do if the credential or repo is missing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.