Skip to main content
Glama

update_ldap_config

Update your organization's LDAP or Active Directory configuration, modifying only the supplied fields. Enable or disable LDAP login without affecting other settings.

Instructions

Update the LDAP / Active Directory configuration for the current organisation.

Only supplied fields are updated — omitted fields are left unchanged. To enable LDAP (ldap_enabled=True), ldap_server_url, ldap_bind_dn, ldap_bind_password, and ldap_search_base must already be set (or provided in the same call). Requires org_admin role.

Search filter examples: OpenLDAP : (uid={username}) Active Directory: (sAMAccountName={username}) Azure AD on-prem: (userPrincipalName={username}@domain.com)

Args: ldap_server_url: LDAP server URL, e.g. ldap://dc.corp.local or ldaps://dc.corp.local. ldap_bind_dn: Service account DN, e.g. cn=svc-vibops,ou=users,dc=corp,dc=local. ldap_bind_password: Service account password (stored Fernet-encrypted). ldap_search_base: Search base DN, e.g. ou=users,dc=corp,dc=local. ldap_search_filter: User search filter with {username} placeholder (default: (uid={username})). ldap_default_role: Role assigned to JIT-provisioned users — member, admin, or viewer. ldap_jit_provisioning: If True, unknown users are auto-provisioned on first login. ldap_enabled: Set True to activate LDAP login, False to disable without clearing config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ldap_bind_dnNo
ldap_enabledNo
ldap_server_urlNo
ldap_search_baseNo
ldap_default_roleNo
ldap_bind_passwordNo
ldap_search_filterNo
ldap_jit_provisioningNo
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses partial update behavior, role requirement, and password encryption, but does not detail consequences of disabling LDAP or irreversible effects.

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

Conciseness5/5

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

Well-structured, front-loaded with purpose, followed by behavioral details, prerequisites, and parameter list. Each sentence adds value without redundancy.

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?

Given 8 parameters and no output schema, the description covers parameter meanings, prerequisites, and usage context sufficiently for an agent to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but the description fully documents all 8 parameters with examples, defaults, and notes on password encryption and search filter formatting.

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 states 'Update the LDAP / Active Directory configuration for the current organisation' with a specific verb and resource, clearly distinguishing it from sibling tools like get_ldap_config.

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 explains partial update behavior ('Only supplied fields are updated'), prerequisites for enabling LDAP, required role ('Requires org_admin role'), and provides search filter examples for different LDAP servers.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/VibOpsai/vibops-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server