Skip to main content
Glama

Update application AI config

update_application_ai_config
Destructive

Change how Ankra AI runs on an Application's repository: enable or disable a lane, pick its model, scope it to branches, ignore paths, set custom review instructions, or set its budget - including max_reviews_per_pull_request, the cap on automatic reviews one pull request receives (platform default 3, 0 = no cap). Call get_application_ai_config first: an override REPLACES the organisation's lane wholesale, so any field you omit falls back to the platform default rather than to your organisation's setting. Send override false for a lane to drop the override and follow the organisation again. Only lanes named in the request are touched.

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>",
      "lanes": "<lanes>"
    },
    "name": "update_application_ai_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
lanesYesThe lanes to change. Lanes left out keep whatever they have.
application_idYesThe Application's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / lanes / items / properties / settings / properties / budget / properties / max_reviews_per_pull_request / description
      Previous value: -"Automatic reviews ONE pull request may receive over its lifetime; the platform default is 5, and 0 means no cap. A review asked for by @mentioning Ankra AI is exempt and always runs. Only meaningful on the pull_request lane."New value: +"Automatic reviews ONE pull request may receive over its lifetime; the platform default is 3, and 0 means no cap. A review asked for by @mentioning Ankra AI is exempt and always runs. Only meaningful on the pull_request lane."
    • changedInput schema / properties / lanes / items / properties / settings / properties / budget / properties / max_runs_per_day / description
      Previous value: -"Runs per day across the repository. 0 = no cap."New value: +"Runs per day across the repository; the platform default is 200 on the pull_request, code and actions lanes. 0 = no cap."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the destructive and non-idempotent annotations, it discloses the critical wholesale-replacement behavior and warns that omitted fields fall back to platform defaults rather than organisation settings. It also explains that override false deletes the application override and bounds the blast radius to lanes named in the request.

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 front-loads the purpose, then moves directly to the prerequisite, replacement hazard, override removal, and update scope. Although dense, each of its four sentences conveys operationally important information without filler.

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?

Together with the fully documented schema and safety annotations, it covers the invocation-critical inheritance, omission, deletion, and per-lane scoping behavior needed to use this complex update safely. No output schema is present, but the absence of return-shape prose does not leave a significant selection or invocation gap.

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 already documents the lane fields, override replacement and deletion semantics, defaults, and treatment of unnamed lanes. The description usefully foregrounds max_reviews_per_pull_request and the read-first workflow, but these details largely repeat the schema, so it earns the high-coverage baseline rather than additional parameter credit.

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?

The opening sentence gives a specific verb and resource: changing how Ankra AI runs on an Application's repository, with concrete lane-level capabilities such as model selection, branch scoping, and budgets. This application-repository and lane scope distinguishes it from the getter and broader AI configuration siblings.

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

Usage Guidelines5/5

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

It gives an explicit prerequisite—call get_application_ai_config first—and explains why that read is necessary before updating. It also distinguishes changing an override from removing one with override false, and explains how to limit an update to particular lanes.

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.