Skip to main content
Glama

Get application AI config

get_application_ai_config
Read-only

Read how Ankra AI is configured for an Application's repository: every lane (pull_request, code, actions, skills, previews) with its effective settings, the organisation default those were resolved from, and whether this Application overrides them. This is where the pull-request review budget lives - max_reviews_per_pull_request (automatic reviews per pull request, platform default 3) and max_runs_per_day (platform default 200 on the pull_request, code and actions lanes). Answers 'why did Ankra AI not review this PR' and 'what would I change to make it review more'. Read-only. An Application whose repository has no connected source-control binding answers with binding.connected false and the reason.

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_ai_config"
  }
}

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 already declare readOnlyHint=true, and the description reinforces it ('Read-only') while adding substantive behavior beyond the annotation: the documented platform defaults (3 reviews per PR, 200 runs/day on pull_request, code and actions lanes) and the edge case that an Application without a connected source-control binding returns binding.connected false with a reason. It does not discuss permissions or response shape beyond the field list, but for a read-only tool the disclosure is strong.

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?

Purpose and scope are front-loaded, followed by the budget detail and the diagnostic questions; the density is justified by the amount of configuration being described. It is somewhat long with em-dash-heavy sentences, but no sentence is pure 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?

With no output schema, the description carries the burden of describing the return payload and does so thoroughly: lane list, effective settings, originating org default, override status, budget fields with defaults, and the disconnected-binding edge case. An agent has everything needed to call it and interpret the result.

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 single parameter application_id is fully documented in the schema (100% coverage), so the description does not need to redefine it. The description adds no syntax or scoping detail for that id beyond referring to the 'Application's repository', which is why this sits at the baseline rather than above it.

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 how Ankra AI is configured for an Application's repository') and then enumerates the exact contents of the response (every lane: pull_request, code, actions, skills, previews; effective settings; org default; override flag). This is far more precise than the title and lets an agent distinguish it from sibling config readers such as get_application_demo_config or get_sops_config.

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?

Supplies concrete decision contexts - diagnosing 'why did Ankra AI not review this PR' and planning 'what would I change to make it review more' - which implicitly positions it as the read counterpart to update_application_ai_config. It does not explicitly name that sibling or state exclusions, so the mapping is left slightly to inference.

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.