Skip to main content
Glama

Infrastructure overview

get_infrastructure
Read-onlyIdempotent

High-level infrastructure overview: components by layer (users, edge, application, data, backup, identity, monitoring, external) and type, provider/region, network zone, internet exposure, authentication, the security controls on each component, and the connections between components (e.g. "Web application → Customer database (mTLS)").

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": {
      "trust_center": "<trust_center>"
    },
    "name": "get_infrastructure"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoOptional language code for translated content (bg, cs, da, de, el, en, es, et, fi, fr, ga, hr, hu, it, lt, lv, mt, nl, pl, pt, ro, sk, sl, sv). Defaults to the original language.
trust_centerYesTrust center id (from list_trust_centers), its domain or the exact company name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

The annotations already establish that this is a safe, read-only, idempotent, non-destructive operation, so the description does not need to repeat safety details. It adds meaningful behavioral context by describing the exact scope of returned data, including layered component groupings and connection relationships, which helps an agent understand what information will be available.

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?

The description is a single front-loaded sentence that lists the returned content efficiently without filler or repetition. It could be slightly easier to scan if the many content categories were separated more clearly, but it remains compact and purposeful.

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 what the tool returns, and it does so thoroughly by enumerating component groupings, attributes, controls, and connection details. The main remaining gap is that it does not distinguish this tool's output from the sibling get_overview, but it is otherwise complete for a read-only overview operation.

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 description coverage is 100%, so both parameters are fully documented in the schema, including the trust_center identifier and optional language code. The description adds no parameter-specific semantics beyond what the schema already provides, making the baseline score of 3 appropriate.

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 clearly states the resource: a high-level infrastructure overview, with explicit coverage of layers, component types, provider/region, exposure, authentication, controls, and connections. This is specific enough to understand the tool's purpose, but it does not explicitly differentiate it from the sibling get_overview, which likely returns a broader trust center overview.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives such as get_overview or list_controls. Usage is only implied by the content listed, and there are no exclusions or stated prerequisites beyond what the schema already requires.

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.

Resources