Skip to main content
Glama
sanyambassi

thales-cdsp-csm-mcp-server

by sanyambassi

manage_targets

Manage external system connections and integrations by listing, creating, retrieving, and deleting database, LDAP, and cloud targets.

Instructions

TARGET MANAGEMENT TOOL - Manage external system connections and integrations

SUPPORTED ACTIONS: • list: Discover all configured targets with filtering • get: Retrieve detailed target configuration and credentials • create: Create new database or LDAP targets • delete: Delete individual target with version control • delete_targets: Bulk delete targets within a specific path

SUPPORTED TARGET TYPES: • Database: MySQL, PostgreSQL, MSSQL, Oracle, Snowflake, MongoDB, Cassandra, HanaDB, Redshift, Redis • LDAP: OpenLDAP, Active Directory • Cloud: AWS, Azure, GCP

Example: Create a MySQL database target for application connections

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pwdNoPassword (REQUIRED for database targets)
sslNoEnable/Disable SSL connection to database
hostNoHost address or endpoint (REQUIRED for database targets)
jsonNoReturn structured JSON output for programmatic processing. Use TRUE when integrating with automation scripts or other tools
nameNoExact target name or identifier (REQUIRED for 'get' and 'create' actions). Examples: 'prod-mysql-db', 'aws-production', 'k8s-cluster-west'
pathNoPath to delete targets from (for delete_targets action)
portNoPort number (optional, uses default if not specified)
actionYesTarget management action to perform. SUPPORTED ACTIONS: 'list' (discover all targets with filtering), 'get' (retrieve detailed target configuration), 'create' (create new database/LDAP targets), 'delete' (delete individual target), 'delete_targets' (bulk delete targets by path)
filterNoPattern to filter target names (for 'list' action). Supports wildcards. Examples: 'prod-*', '*database*', 'aws-*'
bind_dnNoBind DN (REQUIRED for LDAP targets)
db_nameNoDatabase name (REQUIRED for database targets)
db_typeNoDatabase type for database targets. Supported values: 'mysql', 'mssql', 'hanadb', 'postgres', 'mongodb', 'snowflake', 'oracle', 'cassandra', 'redshift', 'redis'
ldap_urlNoLDAP Server URL (REQUIRED for LDAP targets)
uid_tokenNoUniversal identity authentication token. Only required when using universal_identity authentication instead of standard API key authentication
user_nameNoUsername (REQUIRED for database targets)
descriptionNoDescription of the target for documentation and management purposes
server_typeNoLDAP server type. Options: 'OpenLDAP', 'ActiveDirectory'OpenLDAP
target_typeNoType of target to create (REQUIRED for 'create' action). Examples: 'database', 'ldap', 'aws', 'azure', 'gcp', 'k8s', 'ssh'
cluster_modeNoEnable cluster mode for high availability (database targets)
ldap_ca_certNoCA Certificate File Content for LDAP
max_versionsNoMaximum number of versions to keep for the target
target_typesNoFilter by specific target types. SUPPORTED: ['mysql', 'postgres', 'mongodb', 'aws', 'azure', 'gcp', 'k8s', 'ssh', 'ldap', 'github', 'dockerhub', 'artifactory', 'salesforce', 'snowflake', 'redshift', 'mssql', 'cassandra', 'hanadb', 'rabbitmq', 'venafi', 'chef', 'web', 'gke', 'eks', 'oracle']. Use multiple types as array.
mongodb_atlasNoEnable MongoDB Atlas specific configuration
show_versionsNoInclude complete version history and configuration changes for the target (for 'get' action). Essential for audit trails and rollback scenarios
db_server_nameNoServer name for certificate verification
force_deletionNoEnforce deletion (bypass protection)
protection_keyNoProtection key name for encrypting target secrets (uses account default if not specified)
target_versionNoTarget version (for 'get' action: retrieve specific version, for 'delete' action: delete specific version). Use 0 for latest, positive integers for specific versions, or omit for current active version
azure_client_idNoAzure client ID for cloud identity authentication
azure_tenant_idNoAzure tenant ID for cloud identity authentication
connection_typeNoType of connection to database. Options: 'credentials', 'cloud-identity', 'wallet', 'parent-target'credentials
ssl_certificateNoSSL connection certificate data
bind_dn_passwordNoBind DN Password (REQUIRED for LDAP targets)
pagination_tokenNoContinuation token for large result sets. Automatically provided in previous response metadata when more results are available
token_expirationNoToken expiration for LDAP
snowflake_accountNoSnowflake account identifier
parent_target_nameNoName of the parent target (required when connection-type is 'parent-target')
azure_client_secretNoAzure client secret for cloud identity authentication
mongodb_uri_optionsNoMongoDB server URI options
oracle_service_nameNoOracle database service name
cloud_service_providerNoCloud service provider (currently supports Azure)
db_server_certificatesNoDatabase server certificates for verification
mongodb_default_auth_dbNoMongoDB server default authentication database
mongodb_atlas_project_idNoMongoDB Atlas project ID
oracle_wallet_login_typeNoOracle Wallet login type (password/mtls)
snowflake_api_private_keyNoSnowflake RSA private key (base64 encoded)
oracle_wallet_p12_file_dataNoOracle wallet p12 file data in base64
oracle_wallet_sso_file_dataNoOracle wallet sso file data in base64
mongodb_atlas_api_public_keyNoMongoDB Atlas API public key
mongodb_atlas_api_private_keyNoMongoDB Atlas API private key
snowflake_api_private_key_passwordNoSnowflake private key passphrase

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

With no annotations, the description must carry the full burden of disclosing behavioral traits, but it only mentions version control for delete and high-level actions. It does not disclose safety implications, permission requirements, side effects of create/delete, or any special behaviors like pagination or credential handling, which are critical for a tool handling external connections.

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 well-structured with clear sections for actions and target types, and it is front-loaded with the tool purpose. It avoids excessive wordiness while providing an informative overview, though the uppercase heading and repetitive formatting could be slightly tighter.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having an output schema and rich parameter descriptions, the description lacks critical context for a high-complexity tool. It does not clarify which parameters apply to which actions, omits safety/versioning details beyond a mention, and creates ambiguity by stating create supports database/LDAP while the schema includes cloud types. This leaves gaps that could confuse an AI agent.

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 the baseline is 3 since parameter details are already well-documented within the schema. The description adds limited value by listing target types and an example, but it does not deepen understanding of parameter relationships or action-specific requirements beyond what the schema provides.

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 identifies the tool as managing targets (external system connections/integrations) and lists specific supported actions (list, get, create, delete, delete_targets). While 'manage' is a generic verb, the action list provides concrete functionality and distinguishes it from other management tools.

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

Usage Guidelines3/5

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

The description implies usage context by framing targets as external connections and listing actions/types, but it does not explicitly state when to use this tool versus alternatives like manage_secrets or manage_account. There are no exclusions or comparative guidance, leaving usage partially implied rather than clearly directed.

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/sanyambassi/thales-cdsp-csm-mcp-server'

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