Skip to main content
Glama

Get AI environment

get_ai_environment
Read-only

Get the organisation's AI environment settings: the staging cluster ephemeral AI workspaces and PR demos deploy to (with its live agent state), the workspace and demo TTLs, the per-role demo TTL caps, the demo preview domain overrides (demo_base_domain, demo_ingress_class_name, demo_tls_secret_name), and the root domain the organisation's DNS zones hang off (dns_root_domain, the organisation's own custom domain when set; dns_root_domain_default reports the platform default). Call this before deploying a PR demo or workspace to check the staging cluster is configured and online, and to answer why a demo lane refused. Complements get_preview_domain, which resolves the DNS zones the settings hang off. 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_ai_environment"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the closing 'Read-only' is largely redundant, but the description adds genuine context beyond the annotations: it discloses that the returned staging cluster carries 'live agent state' and that the data can explain a refused demo lane. It does not discuss permissions, failure modes, or staleness of the live state, so it stops short of fully rich behavioral disclosure.

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?

It is front-loaded with the core purpose and every clause maps to a real returned field, which matters because there is no output schema. However, it is delivered as two very long sentences with a dense field-name enumeration that would scan better as a short list, and the trailing 'Read-only' duplicates the annotation.

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?

There is no output schema, so the description must carry the burden of describing return content, and it does so thoroughly — TTLs, per-role caps, domain override fields, and DNS root semantics including the default vs override distinction. Combined with a clear pre-deploy check use case, an agent has everything needed to call it correctly.

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?

With zero input parameters there is nothing to disambiguate, which is the baseline-4 case. The description usefully spends its space on output semantics instead, describing the fields the caller will receive.

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 description opens with a specific verb+resource ('Get the organisation's AI environment settings') and then enumerates exactly what the payload contains: staging cluster with live agent state, workspace/demo TTLs, per-role TTL caps, demo domain overrides, and dns_root_domain. It explicitly positions itself against the sibling get_preview_domain, so an agent can distinguish the two without opening either schema.

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 states concrete when-to-use conditions: 'Call this before deploying a PR demo or workspace to check the staging cluster is configured and online, and to answer why a demo lane refused.' It also names the complementary alternative (get_preview_domain, which resolves the DNS zones) and what this tool does that the other does not, leaving little 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.