Skip to main content
Glama

get_integration_auth_posture

Read-only

Retrieves inbound integration authentication posture: Basic auth restrictions and allowlists, OAuth clients, credential aliases, and recent failed logins. Read-only.

Instructions

Inbound integration authentication posture: the Basic auth restriction properties (Brazil allowlist with tracking and enforce modes), accounts allowed to keep Basic auth (snc_basic_auth_api_access role, web service access only users), the Basic auth usage tracker when readable, OAuth clients by grant type and token format (JWT is needed for MCP and A2A), CIMD clients, credential aliases and recent failed logins. 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_integration_auth_posture"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows per list (default 25)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description's trailing 'Read-only' merely repeats that. The value-add is elsewhere: it discloses that the Basic auth usage tracker is returned 'when readable', signaling that some sections may be absent, and it explains the significance of token format (JWT required for MCP/A2A). It stops short of describing pagination behavior across the multiple lists or any permission requirements.

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 category label is front-loaded as a colon-prefixed header, and every enumerated item conveys real content about what is returned. It is a single long run-on sentence with heavy parentheticals, and the final 'Read-only' is redundant, but there is little fat to cut.

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 and a multi-section return payload, the description carries the burden of explaining results, and it does so thoroughly by listing each section and its meaning. Gaps remain around ordering, pagination across multiple lists, and scope per instance, but an agent can understand what it will receive.

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 (limit, default 25) is fully documented in the schema as 'Max rows per list'. The description never mentions it, and because it enumerates several distinct lists, an agent gets no clarification on whether the limit applies per list or overall. With 100% schema coverage the baseline of 3 applies.

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 the specific resource ('Inbound integration authentication posture') and enumerates exactly what the tool surfaces: Basic auth restriction properties with Brazil allowlist modes, accounts allowed to keep Basic auth (snc_basic_auth_api_access, web-service-only users), the usage tracker, OAuth clients by grant type/token format, CIMD clients, credential aliases and failed logins. This is far more specific than a restated title. It does not explicitly distinguish itself from the sibling get_acl_posture, which is the only thing keeping it from a 5.

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?

There is no statement of when to reach for this tool versus get_acl_posture or the other posture/asset tools, and no prerequisites or exclusions are given. Usage is only implied by the subject matter (an audit of inbound integration authentication). The note that 'JWT is needed for MCP and A2A' is domain context about the data, not guidance about invoking this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools