Skip to main content
Glama

Get application setup proposal

get_application_setup_proposal
Read-only

Read the setup Ankra generated for an Application before anything is deployed: the detected language and framework, the setup pull request it opened, whether it generated a database (a CloudNativePG PostgreSQL cluster) and which manifest declares it, and the deploy option contract of record from the repository's .ankra/ankra.yaml - the same options the deploy form renders and the deploy endpoint validates inputs against. negotiable_options lists exactly what revise_application_setup can change. The contract and database members each carry a three-valued status: 'recorded' (read successfully), 'absent' (recorded and genuinely not there) or 'unknown' (nothing recorded, or the recorded file could not be read) - never report an 'unknown' as though Ankra proposed nothing. Read this before revising. Read-only.

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": {
      "application_id": "<application_id>"
    },
    "name": "get_application_setup_proposal"
  }
}

Input Schema

NameRequiredDescriptionDefault
application_idYesThe Application's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds substantial value beyond that by defining the three-valued status semantics ('recorded'/'absent'/'unknown') and warning against misreporting 'unknown' as no proposal. For a read tool with no output schema, this return-value semantics is exactly the sort of disclosure that matters, though it omits anything about latency, permissions, or what happens if no proposal exists at all.

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?

Content is front-loaded with the purpose and the status vocabulary is introduced only where needed. The middle sentence is dense and long, but every clause carries real information (return fields, contract source, validation relationship), so it stays efficient even if it could be split for readability.

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

Completeness5/5

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

With no output schema and only one annotated parameter, the description must carry the return-shape burden, and it does: it enumerates the members returned, explains the status tri-state for contract and database, and links the contract to the deploy form and endpoint. Nothing an agent needs to interpret or safely call this tool appears to be missing.

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?

There is a single parameter and schema description coverage is 100%, so the schema already documents application_id fully. The description refers to 'an Application' but adds no format, sourcing, or lookup detail beyond the schema, so the baseline of 3 applies.

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

Purpose5/5

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

Opens with a specific verb and resource ('Read the setup Ankra generated for an Application') and immediately scopes it ('before anything is deployed'), then enumerates the concrete payload: detected language/framework, setup PR, database cluster and manifest, and the deploy option contract from .ankra/ankra.yaml. That is enough for an agent to distinguish it from siblings like get_application or revise_application_setup without opening the schema.

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?

The description gives clear timing ('before anything is deployed') and an explicit prerequisite for the sibling mutation path ('Read this before revising'), plus it names negotiable_options as exactly what revise_application_setup can change. It stops short of stating when NOT to use it or what to do if the proposal is missing, but the intended usage context is unambiguous.

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.