Skip to main content
Glama

Create an Application

create_application

Create this Project's Application with the outcome in the person's own terms, and record the caller as its builder. Then call describe_application with the application_id it returns.

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": {
      "outcome": "<outcome>"
    },
    "name": "create_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoOptional Application name. Omit it to leave the Application unnamed.
outcomeYesThe outcome in the person's own terms, 20 to 2,000 characters.

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=false, idempotentHint=false and openWorldHint=false, so the write and non-idempotent profile is covered structurally. The description's genuine additions are the builder attribution side effect and the fact that an application_id is returned. It says nothing about what happens if the same name or outcome already exists, or about failure conditions, which matters for a non-idempotent create.

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?

Two sentences, front-loaded with the action and the effect, followed by the required follow-up call. Nothing is padding. Minor redundancy comes from repeating the 'outcome in the person's own terms' wording that the schema already specifies.

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

Completeness4/5

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

With no output schema, the description usefully discloses that an application_id is returned and how to use it, which is the key missing piece an agent would otherwise lack. For a two-parameter create tool with full annotations, that is nearly enough; it only omits error and duplicate-handling behavior.

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?

Schema coverage is 100% and both parameters are documented in the schema, including the 20–2,000 character range and the 'omit to leave unnamed' behavior for name. The description largely restates the 'person's own terms' phrasing already present in the schema rather than adding new meaning. Baseline 3 applies when the schema does the heavy lifting.

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 names a specific verb and resource ('Create this Project's Application') and scopes it to the current Project, which separates it from the role and datasource creation siblings. It also states the two effects: the outcome captured and the caller recorded as builder. It stops short of explicitly contrasting with any other creation path, so it is clear but not sibling-differentiated to the highest degree.

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

Usage Guidelines4/5

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

Usage is made clear by the required 'outcome' framing and, unusually, by an explicit next-step instruction: call describe_application with the returned application_id. That sequencing guidance is actionable. There is no when-not-to-use guidance or statement about duplicate/named applications, so it is not a full 5.

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.

Resources