Skip to main content
Glama

Get AI settings

get_ai_settings
Read-only

How the organisation's AI is configured (the twin of ankra ai status and ankra ai autonomy status): the active model provider, which providers have credentials configured (never the keys or endpoint addresses), the model each AI function runs on (stack READMEs, code review, troubleshooting, deploy analysis, CI/CD generation), and the soft autonomy pause - whether autonomous actions are paused, by whom, through which credential and why, which agents the pause turned off and what resume would restore. paused_through names the credential the pause was engaged through and the project it was held to (project_id null for one that reaches the whole organisation); paused_through null means not recorded (the pause predates Ankra recording it) or nothing is paused, never organisation-wide, and a project outside the reader's own is withheld and marked project_outside_projects true. paused_through_note says which. personal_ai_keys_allowed says whether AI work a member starts may run on that member's own AI keys (set_personal_ai_keys_allowed changes it). Read-only. Provider keys are never returned.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_ai_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, yet the description adds genuine substance: keys and endpoint addresses are never returned, a project outside the reader's own is withheld and flagged with project_outside_projects, and null paused_through has specific meanings. These confidentiality and redaction behaviours are exactly the kind of context annotations cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Everything is crammed into a single sprawling sentence of roughly 200 words, and the paused_through explanation degenerates into a run-on ('...never organisation-wide, and a project outside the reader's own is withheld...'). The content is valuable but the structure makes it hard to parse, and field-level detail would be far clearer as a list.

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 carries the burden of explaining return values, and it does so field by field, including null semantics and the redaction rule. It is close to complete; only differentiation from sibling AI-configuration tools is missing.

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?

The tool takes zero parameters, so the baseline is 4. The description instead spends its space documenting response-field semantics, which is the only parameter-like surface available for a no-argument getter.

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 resource and enumerates exactly what is returned: active provider, which providers have credentials, which model each AI function runs on, and the soft autonomy pause. It does not distinguish itself from close siblings such as get_ai_environment or get_application_ai_config, so an agent must infer which of the three to call.

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 is only implied through references to `ankra ai status`, `set_personal_ai_keys_allowed` and the pause semantics, which hint at reading state before mutating it. There is no explicit when-to-use or when-not-use guidance, and no mention of the AI-readable siblings that overlap with this tool.

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.