Skip to main content
Glama

Get ci settings

get_ci_settings
Read-only

Read the organisation's Ankra Pipelines CI configuration: the settings (the CI cluster, the step image policy and retention), the pool of clusters pipelines may run on, and the pool's current capacity. This is what explains a pipeline that ran on an unexpected cluster, a refused step image, or runs that queue for capacity. Read-only.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the bar is lower, yet the description still tells the agent what data is exposed (cluster, step image policy, retention, cluster pool, live capacity) and what symptom each part explains. The trailing 'Read-only.' mildly restates the annotation but does add useful confirmation that no mutation happens. No rate-limit or freshness/auth caveats.

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?

Front-loaded with the resource, then a compact parenthetical breakdown, then one sentence of diagnostic value. Nearly every clause earns its place; only the redundant final 'Read-only.' is disposable.

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 zero parameters, no output schema, and a matching readOnly annotation, the description carries exactly the burden required: it describes the shape of the returned configuration in prose and explains why an agent would fetch it. Nothing needed to call it correctly 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 no parameters, so baseline is 4 and there is nothing further for the description to disambiguate. The schema is an empty object with full coverage, matching the description's implied org-wide, unfiltered read.

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?

Uses a specific verb (read) and a precisely scoped resource (the organisation's Ankra Pipelines CI configuration), then enumerates the three parts: settings (cluster, step image policy, retention), the cluster pool, and its current capacity. Against siblings named get_addon_settings / get_ai_settings / get_cost_settings, the resource qualified as 'CI' is unambiguous.

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?

Gives concrete diagnostic scenarios that select this tool: a pipeline on an unexpected cluster, a refused step image, or runs queuing for capacity. That is strong positive when-to-use guidance, but it names no alternative or exclusion (e.g., when a settings-write tool would be needed instead), so it stops short of a 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.